agents-united 1.0.0 → 1.2.0

package/registry/workflows/workflow-marketing-campaign-builder.md

@@ -1,15 +1,60 @@
-# Workflow: Marketing Campaign Builder
+---
+name: "Multi-Channel Marketing Campaign Construction"
+description: "End-to-end workflow for building integrated marketing campaigns across email, social media, paid ads, and landing pages."
+bundle: "growth-marketing"
+estimatedDuration: "60-120m"
+---
 
-Multi-phase procedural workflow for Marketing Campaign Builder.
+# Workflow: Multi-Channel Marketing Campaign Construction
+
+## Overview & Scope
+The Campaign Builder workflow constructs integrated multi-channel marketing campaigns. It orchestrates landing page creation, email drip sequences, ad creative assets, and UTM tracking parameters.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Context & Reconnaissance]
+    P1 --> InputCheck{"Prerequisites & Tools Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Execution & Orchestration]
+    P2 --> Gate1{"Verification Gate: Automated Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Closure]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Documentation / Artifacts]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Marketing campaign brief & strategy roadmap
+- Channel creative templates (email HTML, ad banners, social posts)
+- UTM parameter taxonomy guidelines
 
 ## Phase 1: Context & Reconnaissance
-- Analyze the user request and existing codebase state.
-- Gather necessary inputs and verify environment readiness.
+- Establish campaign goals (lead generation, feature announcement, webinar signups).
+- Define target channels (Email, Twitter/X, LinkedIn, Google Ads, Meta Ads).
+- Confirm campaign budget, schedule, and UTM tracking structure.
 
 ## Phase 2: Execution & Orchestration
-- Execute core steps with progressive verifications.
-- Delegate sub-tasks to specialized sub-agents.
+- Draft campaign landing page copy and configure opt-in form integration.
+- Write multi-step email nurture sequence (Welcome, Value delivery, Social proof, Offer CTA).
+- Generate ad banner visual assets and social media post copy variations with UTM links.
 
 ## Phase 3: Verification & Closure
-- Run verification tests and linting.
-- Document outcome and present summary.
+- Test campaign links in analytics sandbox to verify UTM parameter tracking.
+- Preview email rendering across email clients (mobile, desktop, dark mode).
+- Publish Campaign Execution Blueprint.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `npm test` | UTM link validator verifies 100% of campaign links contain correct tracking parameters |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm run build` | Email HTML templates and campaign assets build without errors |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: All UTM tracking parameters configured and verified in analytics test environment.
+- **Validation Checkpoint 2**: Campaign copy matches approved brand messaging brief across all channels.
+- **Automated Rollback Protocol**: Pause campaign rollout if link tracking parameters fail to log in analytics test sandbox.

package/registry/workflows/workflow-marketing-content-pipeline.md

@@ -1,15 +1,60 @@
-# Workflow: Marketing Content Pipeline
+---
+name: "Content Engine & SEO Pipeline"
+description: "Workflow for keyword research, content drafting, SEO optimization, editorial review, and content publishing."
+bundle: "growth-marketing"
+estimatedDuration: "45-90m"
+---
 
-Multi-phase procedural workflow for Marketing Content Pipeline.
+# Workflow: Content Engine & SEO Pipeline
+
+## Overview & Scope
+This workflow drives the content engine. It structures keyword research, topic clustering, SEO-optimized article drafting, Schema.org markup validation, and CMS publishing.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Context & Reconnaissance]
+    P1 --> InputCheck{"Prerequisites & Tools Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Execution & Orchestration]
+    P2 --> Gate1{"Verification Gate: Automated Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Closure]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Documentation / Artifacts]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Target search query keyword research data
+- Editorial style guide and content guidelines
+- SEO optimization scanner & Schema.org validator
 
 ## Phase 1: Context & Reconnaissance
-- Analyze the user request and existing codebase state.
-- Gather necessary inputs and verify environment readiness.
+- Identify target search queries, search intent, and top-ranking competitor content.
+- Develop article outline featuring target primary keyword and supporting LSI keywords.
+- Select Schema.org structured data type (Article, BlogPosting, HowTo).
 
 ## Phase 2: Execution & Orchestration
-- Execute core steps with progressive verifications.
-- Delegate sub-tasks to specialized sub-agents.
+- Draft comprehensive content article addressing search intent with depth and clarity.
+- Incorporate internal links to related product pages and authoritative external sources.
+- Write optimized title tag, meta description, H1/H2 headings, and image alt text.
 
 ## Phase 3: Verification & Closure
-- Run verification tests and linting.
-- Document outcome and present summary.
+- Perform readability check (Flesch-Kincaid score) and verify keyword density (1-2%).
+- Validate Schema.org JSON-LD structured data using rich result validator tools.
+- Publish article to CMS repository.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `npm test` | SEO content test suite validates Schema.org JSON-LD syntax |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm run build` | CMS static site generator builds page cleanly |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Article satisfies word count and keyword intent coverage requirements.
+- **Validation Checkpoint 2**: Schema.org structured data passes validation test with zero errors.
+- **Automated Rollback Protocol**: Re-draft article sections if readability grade level falls outside target parameters.

package/registry/workflows/workflow-marketing-growth-experiment.md

@@ -1,15 +1,60 @@
-# Workflow: Marketing Growth Experiment
+---
+name: "A/B Growth Experiment Design & Tracking"
+description: "Workflow for designing A/B split tests, configuring experiment variants, setting up tracking events, and evaluating statistical significance."
+bundle: "growth-marketing"
+estimatedDuration: "35-60m"
+---
 
-Multi-phase procedural workflow for Marketing Growth Experiment.
+# Workflow: A/B Growth Experiment Design & Tracking
+
+## Overview & Scope
+The Growth Experiment workflow structures scientific A/B testing. It defines hypotheses, designs control and challenger variants, configures event tracking, and calculates statistical significance.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Context & Reconnaissance]
+    P1 --> InputCheck{"Prerequisites & Tools Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Execution & Orchestration]
+    P2 --> Gate1{"Verification Gate: Automated Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Closure]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Documentation / Artifacts]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Growth hypothesis statement
+- A/B testing framework / feature flag system (PostHog / LaunchDarkly)
+- Baseline metric conversion rates
 
 ## Phase 1: Context & Reconnaissance
-- Analyze the user request and existing codebase state.
-- Gather necessary inputs and verify environment readiness.
+- Formulate experiment hypothesis: "If [change], then [impact] because [rationale]".
+- Calculate required sample size and test duration for 95% statistical power.
+- Define primary conversion metric and secondary guardrail metrics.
 
 ## Phase 2: Execution & Orchestration
-- Execute core steps with progressive verifications.
-- Delegate sub-tasks to specialized sub-agents.
+- Configure Variant A (Control) and Variant B (Challenger) in experiment platform.
+- Implement analytics event tracking triggers for conversion actions.
+- Run sample ratio mismatch (SRM) test to verify unbiased 50/50 traffic split.
 
 ## Phase 3: Verification & Closure
-- Run verification tests and linting.
-- Document outcome and present summary.
+- Monitor experiment health during initial traffic rollout.
+- Evaluate conversion results once required sample size is reached, calculating p-value.
+- Publish Growth Experiment Results & Learnings report.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `npm test` | Experiment tracking suite validates event logging for both variants |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm run build` | Experiment feature flag code builds without type errors |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Sample ratio mismatch (SRM) test confirms unbiased traffic allocation.
+- **Validation Checkpoint 2**: Statistical significance reaches >= 95% confidence before declaring winning variant.
+- **Automated Rollback Protocol**: Disable challenger experiment variant immediately if conversion drops severely during rollout.

package/registry/workflows/workflow-marketing-launch.md

@@ -1,15 +1,60 @@
-# Workflow: Marketing Launch
+---
+name: "Product Launch Playbook Execution"
+description: "Structured workflow for coordinating product launches across Product Hunt, social channels, press releases, customer emails, and community platforms."
+bundle: "growth-marketing"
+estimatedDuration: "60-120m"
+---
 
-Multi-phase procedural workflow for Marketing Launch.
+# Workflow: Product Launch Playbook Execution
+
+## Overview & Scope
+The Launch workflow coordinates product launch execution. It orchestrates Product Hunt launches, social media announcements, customer email blasts, press releases, and real-time launch operations.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Context & Reconnaissance]
+    P1 --> InputCheck{"Prerequisites & Tools Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Execution & Orchestration]
+    P2 --> Gate1{"Verification Gate: Automated Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Closure]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Documentation / Artifacts]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Product release notes & feature highlights
+- Media kit assets (logos, screenshots, promotional videos)
+- Multi-channel launch checklist
 
 ## Phase 1: Context & Reconnaissance
-- Analyze the user request and existing codebase state.
-- Gather necessary inputs and verify environment readiness.
+- Confirm product stability and verify production environment readiness.
+- Verify all promotional creative, media kits, and link destinations are staged.
+- Align launch team roles and monitoring responsibilities for launch day.
 
 ## Phase 2: Execution & Orchestration
-- Execute core steps with progressive verifications.
-- Delegate sub-tasks to specialized sub-agents.
+- Publish launch post on Product Hunt, Hacker News, Twitter/X, and LinkedIn.
+- Trigger launch email blast to subscriber mailing list.
+- Engage with community comments and answer user feedback in real time.
 
 ## Phase 3: Verification & Closure
-- Run verification tests and linting.
-- Document outcome and present summary.
+- Monitor server infrastructure load, signup conversion rates, and error logs.
+- Compile day-1 launch analytics summary (upvotes, signups, traffic sources).
+- Publish Post-Launch Retrospective report.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `npm test` | Launch checklist validator confirms 100% prerequisite tasks complete |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `node dist/cli.js doctor` | Doctor health check confirms system readiness |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Product onboarding and signup flows verified operational under traffic load.
+- **Validation Checkpoint 2**: All scheduled channel launch posts published successfully.
+- **Automated Rollback Protocol**: Divert traffic to status fallback page if servers experience unexpected downtime during launch.

package/registry/workflows/workflow-marketing-panel.md

@@ -1,15 +1,60 @@
-# Workflow: Marketing Panel
+---
+name: "Marketing & Messaging Review Panel"
+description: "Panel workflow assembling growth, content, copy, and conversion specialists to evaluate marketing positioning and campaigns."
+bundle: "growth-marketing"
+estimatedDuration: "40-70m"
+---
 
-Multi-phase procedural workflow for Marketing Panel.
+# Workflow: Marketing & Messaging Review Panel
+
+## Overview & Scope
+The Marketing Panel workflow evaluates campaign messaging and positioning. It convenes Growth Strategists, Copywriters, and Conversion Specialists to review value propositions, CTA clarity, and brand voice.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Context & Reconnaissance]
+    P1 --> InputCheck{"Prerequisites & Tools Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Execution & Orchestration]
+    P2 --> Gate1{"Verification Gate: Automated Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Closure]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Documentation / Artifacts]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Marketing campaign brief & copy drafts
+- Value proposition canvas and target audience personas
+- Brand positioning guidelines
 
 ## Phase 1: Context & Reconnaissance
-- Analyze the user request and existing codebase state.
-- Gather necessary inputs and verify environment readiness.
+- Gather marketing assets, landing page copy, email drafts, and ad creative.
+- Define evaluation dimensions (Value messaging clarity, Emotional resonance, Call-to-action strength, Brand tone).
+- Distribute copy drafts to marketing panel personas.
 
 ## Phase 2: Execution & Orchestration
-- Execute core steps with progressive verifications.
-- Delegate sub-tasks to specialized sub-agents.
+- Conduct panel review session collecting structured feedback across marketing specialist roles.
+- Audit copy for jargon, ambiguous claims, and value clarity above the page fold.
+- Identify positioning friction and formulate copy optimization suggestions.
 
 ## Phase 3: Verification & Closure
-- Run verification tests and linting.
-- Document outcome and present summary.
+- Synthesize panel feedback into Marketing Review Verdict (Approved, Approved with Copy Edits, Rejected).
+- Draft actionable copy revision guide with line-by-line recommendations.
+- Publish Marketing Panel Review Summary.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `node dist/cli.js doctor` | Doctor health check confirms marketing panel report format |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm test` | Validation tests pass for copy audit report artifacts |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Core value proposition clearly communicated within first fold screen area.
+- **Validation Checkpoint 2**: Zero confusing jargon or unsubstantiated claims in hero section copy.
+- **Automated Rollback Protocol**: Reject campaign copy for re-write if message clarity score falls below evaluation threshold.

package/registry/workflows/workflow-ml-eval.md

@@ -0,0 +1,51 @@
+---
+name: "ML Model Evaluation & Benchmarking Workflow"
+description: "Rigorous model evaluation, synthetic benchmark testing, faithfulness scoring, and Hugging Face scorecard generation."
+bundle: "ai-ml-engineering"
+estimatedDuration: "30-60m"
+---
+
+# Workflow: ML Model Evaluation & Benchmarking
+
+## Overview & Scope
+This workflow coordinates systematic evaluation of fine-tuned and open-source models against standardized benchmark datasets, measuring faithfulness, context relevancy, and inference latency.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Evaluation]) --> P1[Phase 1: Dataset & Metric Configuration]
+    P1 --> InputCheck{"Evaluation Dataset & Golden QA Set Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Validation Dataset]
+    InputCheck -->|Yes| P2[Phase 2: Benchmark Execution & Scoring]
+    P2 --> Gate1{"Verification Gate: Benchmark Run Complete?"}
+    Gate1 -->|Fail| P2Fix[Adjust Batch Size / Re-run Inference]
+    P2Fix --> P2
+    Gate1 -->|Pass| P3[Phase 3: Analysis & Model Card Publish]
+    P3 --> Gate2{"Quality Gate: Accuracy & Faithfulness > Threshold?"}
+    Gate2 -->|Fail| FlagModel[Flag Model for Retraining / Prompt Tuning]
+    Gate2 -->|Pass| Done([Model Evaluation Signed Off])
+```
+
+## Phase 1: Dataset & Metric Configuration
+- Load golden QA evaluation splits or standardized benchmarks (MMLU, GSM8k, Ragas synthetic testsets).
+- Define evaluation thresholds (e.g. Faithfulness >= 0.85, Answer Relevance >= 0.80).
+
+## Phase 2: Benchmark Execution & Scoring
+- Execute deterministic batch inference across evaluation splits with fixed random seeds.
+- Compute automated metrics (Exact Match, BLEU/ROUGE, Ragas LLM-as-a-judge scores).
+
+## Phase 3: Analysis & Model Card Publish
+- Analyze error distribution and hallucination clusters.
+- Generate Hugging Face model evaluation scorecard and publish metrics summary.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Datasets validated | `node dist/cli.js doctor` | Evaluation harness initialized |
+| Phase 2 -> Phase 3 | Scoring complete | `npm test` | Benchmark outputs parsed into structured metrics |
+| Phase 3 -> Completion | Metrics meet quality bar | `node dist/cli.js doctor` | Scorecard published and verified |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Verify dataset schema compliance and label distributions before starting benchmark run.
+- **Validation Checkpoint 2**: Ensure deterministic seed produces identical predictions on sample batch.
+- **Automated Rollback Protocol**: If evaluation reveals critical toxicity regression or accuracy drop > 5%, revert model deployment target to previous checkpoint baseline and emit alert.

package/registry/workflows/workflow-mobile-build.md

@@ -0,0 +1,49 @@
+---
+name: "Mobile Multi-Platform Build & Verification"
+description: "Workflow for executing cross-platform mobile builds (iOS/Android/Expo), verifying asset bundle sizes, and checking native compilation status."
+bundle: "mobile-development"
+estimatedDuration: "15-30m"
+---
+
+# Workflow: Mobile Multi-Platform Build & Verification
+
+## Overview & Scope
+The Mobile Build workflow compiles native and cross-platform mobile application packages (IPA / APK / AAB / Expo EAS), validating binary size, asset optimization, and compiler flags.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Environment & Dependency Check]
+    P1 --> InputCheck{"Podfile & Gradle Ready?"}
+    InputCheck -->|No| Abort1[Abort & Resolve Dependencies]
+    InputCheck -->|Yes| P2[Phase 2: Compilation & Asset Bundling]
+    P2 --> Gate1{"Verification Gate: Compilation Exit Code 0?"}
+    Gate1 -->|Fail| Rollback[Inspect Build Logs & Fix Compilation Errors]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Binary Inspection & Artifact Sign-off]
+    P3 --> Done([Mobile Build Package Ready])
+```
+
+## Required Tool Inputs & Context
+- Target mobile platform (`ios`, `android`, `all`)
+- Build type (`debug`, `release`)
+- Xcode / Android SDK environment setup
+
+## Phase 1: Environment & Dependency Check
+- Inspect native configuration files (`Podfile`, `build.gradle`, `app.json`).
+- Verify signing identities and bundle identifiers.
+
+## Phase 2: Compilation & Asset Bundling
+- Execute compilation (`xcodebuild` / `./gradlew assembleRelease` / `eas build --local`).
+- Check output for deprecated API usages or symbol collision warnings.
+
+## Phase 3: Binary Inspection & Artifact Sign-off
+- Audit final binary file size against mobile app budget (< 50MB target).
+- Verify entry point manifest and permission declarations.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Dependencies resolved | `npm run lint` / `pod install` | Dependency graph clean with 0 lockfile errors |
+| Phase 2 -> Phase 3 | Compilation completed | `npm run build:mobile` | Binary generated with exit code 0 |
+| Phase 3 -> Completion | Binary signed and verified | Binary size & signature audit | Target package bundle verified |

package/registry/workflows/workflow-onboarding-funnel-cro.md

@@ -0,0 +1,65 @@
+---
+name: "Product-Led Onboarding Funnel & Conversion Rate Optimization"
+description: "Workflow for auditing user onboarding drop-off, designing activation experiments, optimizing signup flows, and engineering viral referral loops."
+bundle: "product-led-growth"
+estimatedDuration: "45-75m"
+---
+
+# Workflow: Product-Led Onboarding Funnel & Conversion Rate Optimization
+
+## Overview & Scope
+The Onboarding Funnel CRO workflow accelerates user activation and Product-Led Growth (PLG). It conducts funnel drop-off diagnostics, form friction reduction, interactive onboarding checklist deployment, time-to-value (TTV) optimization, and viral referral loop engineering.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Funnel Diagnostic & Telemetry Audit]
+    P1 --> InputCheck{"Telemetry & Baseline Metrics Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Funnel Data]
+    InputCheck -->|Yes| P2[Phase 2: Onboarding Experimentation & Interaction Optimization]
+    P2 --> Gate1{"Verification Gate: Event Tracking & A/B Flags Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Telemetry Verification, SRM Audit & Rollout]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Funnel Code / Flags]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Onboarding funnel step definitions (Signup -> Profile -> First Project -> Aha Moment -> Activation)
+- Baseline conversion telemetry (step-by-step drop-off rates, time-to-value benchmarks)
+- Feature flag / experimentation platform configuration (PostHog, LaunchDarkly, GrowthBook)
+- Product onboarding UI component library (checklists, tooltips, empty states)
+
+## Phase 1: Funnel Diagnostic & Telemetry Audit
+- Map user journey milestones from initial landing to core product activation.
+- Analyze step-by-step drop-off metrics to identify primary conversion bottlenecks.
+- Calculate baseline Time-to-Value (TTV) and identify friction points (unnecessary form fields, password friction, premature paywalls).
+- Formulate CRO hypothesis: "By replacing [friction point] with [optimized interaction], activation rate will increase by [X]%".
+
+## Phase 2: Onboarding Experimentation & Interaction Optimization
+- Design optimized challenger variant (frictionless OAuth/magic link, progressive profiling, interactive onboarding checklist).
+- Pre-fill empty states with actionable starter templates to accelerate the "Aha!" moment.
+- Integrate viral referral mechanics (team invite prompts, shared workspace links, gamified completion rewards).
+- Configure A/B test feature flags with deterministic 50/50 user hashing.
+
+## Phase 3: Telemetry Verification, SRM Audit & Rollout
+- Verify analytics event emission across all onboarding milestone steps.
+- Execute Sample Ratio Mismatch (SRM) test to confirm unbiased 50/50 traffic split between control and challenger variants.
+- Monitor error logs, user drop-offs, and completion rates in real time during initial rollout.
+- Evaluate statistical significance (p < 0.05) once required sample size is reached.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `npm test` | Onboarding test suite validates event tracking triggers and feature flag routing logic |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm run build` | Frontend UI components and onboarding bundle compile without TypeScript errors |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: All onboarding milestone events fire consistently with valid user and workspace IDs.
+- **Validation Checkpoint 2**: Sample Ratio Mismatch (SRM) chi-square test passes with p > 0.01, confirming unskewed variant distribution.
+- **Validation Checkpoint 3**: Challenger variant demonstrates zero regression in critical registration flows.
+- **Automated Rollback Protocol**: Automatically switch feature flag to 100% control variant and disable challenger flow if onboarding error rate spikes by > 2% or completion rate drops significantly during rollout.

package/registry/workflows/workflow-paid-acquisition-campaign.md

@@ -0,0 +1,65 @@
+---
+name: "Multi-Channel Paid Acquisition Campaign Management"
+description: "Workflow for multi-channel PPC campaign architecture, ad copy experimentation, creative asset staging, attribution setup, and budget guardrails."
+bundle: "performance-paid-acquisition"
+estimatedDuration: "60-120m"
+---
+
+# Workflow: Multi-Channel Paid Acquisition Campaign Management
+
+## Overview & Scope
+The Paid Acquisition Campaign workflow structures end-to-end PPC campaign deployment across Google Ads, Meta Ads, and LinkedIn Ads. It covers audience targeting, ad copy matrix generation, creative aspect-ratio staging, UTM parameter taxonomy enforcement, and multi-touch attribution modeling.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Campaign Strategy & Attribution Setup]
+    P1 --> InputCheck{"Budgets & Audience Parameters Valid?"}
+    InputCheck -->|No| Abort1[Abort & Request Budget/Targeting Inputs]
+    InputCheck -->|Yes| P2[Phase 2: Creative Generation & Ad Staging]
+    P2 --> Gate1{"Verification Gate: Creative & UTM Checks Pass?"}
+    Gate1 -->|Fail| Rollback[Execute Automated Rollback Protocol]
+    Rollback --> P2
+    Gate1 -->|Pass| P3[Phase 3: Verification & Controlled Launch]
+    P3 --> Gate2{"Final Acceptance Gate Passed?"}
+    Gate2 -->|Fail| P3Fix[Remediate Ad Specs / Pixel Issues]
+    P3Fix --> P3
+    Gate2 -->|Pass| Done([Workflow Complete & Logged])
+```
+
+## Required Tool Inputs & Context
+- Campaign brief & target audience personas (interests, job titles, retargeting lists)
+- Channel allocation and daily/monthly spend budget caps
+- Creative assets (ad copy matrix, visual banners, video cuts)
+- UTM taxonomy specification and attribution tracking endpoint
+
+## Phase 1: Campaign Strategy & Attribution Setup
+- Define campaign objective (Leads, Conversions, Brand Awareness) and channel distribution (Google Search/PMax, Meta, LinkedIn).
+- Configure audience targeting rules: Custom Audiences, Lookalikes, keyword match types (Exact/Phrase), and negative keyword lists.
+- Establish UTM parameter taxonomy (`utm_source`, `utm_medium`, `utm_campaign`, `utm_content`, `utm_term`).
+- Verify conversion tracking pixels and server-side Conversions API (CAPI) endpoints.
+
+## Phase 2: Creative Generation & Ad Staging
+- Write multi-variant ad copy matrix (Headline variations, Primary text, Problem-Agitation, Social proof, CTA).
+- Stage visual creative assets formatted for channel aspect ratios (1:1 Feed, 9:16 Stories/Reels, 16:9 Landscape).
+- Verify landing page message match and conversion form functionality.
+- Configure bid strategy (Target CPA, Target ROAS, Max Conversions with hard cost cap).
+
+## Phase 3: Verification & Controlled Launch
+- Validate tracking pixels in sandbox environment using Tag Assistant / Pixel Helper tools.
+- Test all ad destination URLs to confirm UTM parameters log accurately in attribution backend.
+- Enforce daily spend hard caps and automated pacing rules to prevent budget runaway.
+- Execute canary launch with controlled initial spend (10-20% of daily budget) before full scale.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tool inputs verified & environment ready | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Execution steps complete | `npm test` | Ad asset validator confirms 100% adherence to character limits, aspect ratios, and UTM parameters |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm run build` | Campaign launch manifest and tracking configuration compile cleanly |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: 100% of destination URLs contain valid UTM parameters matching the attribution taxonomy.
+- **Validation Checkpoint 2**: Ad creative dimensions and copy lengths comply with platform ad policies (Google, Meta, LinkedIn).
+- **Validation Checkpoint 3**: Daily budget spend ceilings and automated pacing rules are active in ad accounts.
+- **Automated Rollback Protocol**: Immediately trigger automated pause API calls on active ad sets and revert campaign status to DRAFT if conversion tracking fails to log in attribution telemetry or spend velocity exceeds 120% of hourly target without conversions.

package/registry/workflows/workflow-paid-campaign-launch.md

@@ -0,0 +1,47 @@
+---
+name: "Paid Campaign Architecture & Launch Workflow"
+description: "PPC campaign setup, ad copy testing, conversion tracking pixel verification, and launch budgeting."
+bundle: "performance-paid-acquisition"
+estimatedDuration: "45-90m"
+---
+
+# Workflow: Paid Campaign Architecture & Launch
+
+## Overview & Scope
+This workflow orchestrates paid acquisition campaigns across Google Search, Meta Ads, and LinkedIn, ensuring proper conversion tracking, negative keyword lists, and creative variant testing.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Campaign Launch]) --> P1[Phase 1: Conversion Tracking & Pixel Audit]
+    P1 --> InputCheck{"Pixels, CAPI & UTM Parameters Configured?"}
+    InputCheck -->|No| Abort1[Abort & Configure Conversion Tracking]
+    InputCheck -->|Yes| P2[Phase 2: Ad Copy, Creative & Keyword Assembly]
+    P2 --> Gate1{"Verification Gate: Negative Lists & Creative Sizing Valid?"}
+    Gate1 -->|Fail| P2Fix[Update Keyword Match Types & Asset Sizes]
+    P2Fix --> P2
+    Gate1 -->|Pass| P3[Phase 3: Campaign Publishing & Real-Time Monitoring]
+    P3 --> Gate2{"Health Gate: CTR >= Baseline & Zero Tracking Errors?"}
+    Gate2 -->|Fail| P3Tune[Adjust Initial Bid Caps / Ad Copy Variants]
+    P3Tune --> P3
+    Gate2 -->|Pass| Done([Campaign Live & Tracking])
+```
+
+## Phase 1: Conversion Tracking & Pixel Audit
+- Verify Google Tag Manager / Meta Pixel / LinkedIn Insight Tag firing on conversion events.
+- Test server-side Conversions API (CAPI) deduplication.
+
+## Phase 2: Ad Copy, Creative & Keyword Assembly
+- Group keywords into tightly themed ad sets and apply universal negative keyword lists.
+- Stage 3-5 creative hook variants and responsive ad copy variations.
+
+## Phase 3: Campaign Publishing & Real-Time Monitoring
+- Publish campaigns with initial learning phase budget caps.
+- Monitor search term reports for irrelevant query leakage and add negative keywords.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tracking active | `node dist/cli.js doctor` | Conversion pixels and test events verified |
+| Phase 2 -> Phase 3 | Assets assembled | `npm test` | All creative dimensions and copy lengths valid |
+| Phase 3 -> Completion | Campaigns live | `node dist/cli.js doctor` | Impressions recording with verified attribution |