agents-united 0.5.0

package/registry/workflows/workflow-agency-brand-design-system.md

@@ -0,0 +1,50 @@
+---
+name: "Agency Brand Design System & Component Library"
+description: "Tokenized design system architecture, Figma token sync, Tailwind color palettes, and Storybook interactive component playground setup."
+bundle: "digital-agency"
+estimatedDuration: "60-120m"
+---
+
+# Workflow: Agency Brand Design System & Component Library
+
+## Overview & Scope
+Builds scalable, production-grade design systems with design tokens, typography ramps, UI component contracts, and Storybook interactive playgrounds.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Brand Guidelines]) --> P1[Phase 1: Token Architecture & Ramp Extraction]
+    P1 --> P2[Phase 2: Component Library & Spec Construction]
+    P2 --> Gate1{"Tokens & WCAG AA Verified?"}
+    Gate1 -->|Fail| P2
+    Gate1 -->|Pass| P3[Phase 3: Storybook & Documentation Export]
+    P3 --> Done([Design System Shipped])
+```
+
+## Required Tool Inputs & Context
+- Brand guidelines, logo marks, and primary/secondary colors
+- Figma MCP / Stitch MCP / local CSS token definitions
+- Storybook / component playground configs
+
+## Phase 1: Token Architecture
+- Define semantic tokens (colors, spacing, radii, typography ramps, shadows).
+- Establish light/dark mode color pairings.
+
+## Phase 2: Component Specifications
+- Build core component contracts (Button, Input, Card, Modal, Nav).
+- Ensure WCAG 2.2 AA accessibility and focus states.
+
+## Phase 3: Verification & Storybook Integration
+- Spin up component sandbox via `manage_task` or static build.
+- Export token documentation and Tailwind CSS preset.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Tokens declared | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Components implemented | `npm run typecheck` | TypeScript component interfaces compile cleanly |
+| Phase 3 -> Completion | Visual contracts verified | `npm run build` | Storybook / component assets build without errors |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: All color contrast ratios meet or exceed 4.5:1 for normal text.
+- **Automated Rollback Protocol**: Adjust hue and luminosity values if contrast checker fails.

package/registry/workflows/workflow-agency-client-pitch-proposal.md

@@ -0,0 +1,50 @@
+---
+name: "Agency Client Pitch Proposal & Scoping Blueprint"
+description: "Cross-functional client discovery, pitch deck ingestion, technical scope estimation, and executive agency proposal blueprint creation."
+bundle: "digital-agency"
+estimatedDuration: "45-75m"
+---
+
+# Workflow: Agency Client Pitch Proposal & Scoping Blueprint
+
+## Overview & Scope
+Transforms raw client discovery calls, RFPs, or PDF pitch decks into a comprehensive, high-impact digital agency project proposal and scoping blueprint.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Client RFP / Ingest]) --> P1[Phase 1: Multi-Agent Discovery & Sizing]
+    P1 --> P2[Phase 2: Milestone Blueprint & SOW Generation]
+    P2 --> Gate1{"Executive Review Passed?"}
+    Gate1 -->|Fail| P2
+    Gate1 -->|Pass| P3[Phase 3: Client Proposal Delivery]
+    P3 --> Done([Proposal Ready])
+```
+
+## Required Tool Inputs & Context
+- Client RFP, discovery call transcripts, or PDF pitch deck
+- MarkItDown MCP / voice memo ingestion
+- Agency rate card and milestone estimation framework
+
+## Phase 1: Context & Discovery Sizing
+- Ingest client materials and extract core functional requirements.
+- Calculate timeline estimates across Design, Engineering, and Growth.
+
+## Phase 2: SOW & Milestone Architecture
+- Structure deliverables into vertical phased milestones (M1–M4).
+- Define Acceptance Criteria, SLA expectations, and risk contingencies.
+
+## Phase 3: Verification & Packaging
+- Verify timeline feasibility and budget alignment with Director (`chris-director`).
+- Output executive markdown proposal and client presentation outline.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Sizing completed | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Proposal drafted | `npm test` | Proposal validator confirms all deliverables have explicit acceptance criteria |
+| Phase 3 -> Completion | Final review complete | `npm run build` | Proposal documentation renders with 0 errors |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Every vertical milestone has measurable success criteria.
+- **Automated Rollback Protocol**: Re-scope deliverables if total project duration exceeds client deadline.

package/registry/workflows/workflow-agency-cro-funnel-teardown.md

@@ -0,0 +1,50 @@
+---
+name: "Agency CRO Funnel Teardown & Onboarding Optimization"
+description: "Conversion Rate Optimization audit, onboarding friction teardown, signup flow experiment design, and Playwright automated testing."
+bundle: "digital-agency"
+estimatedDuration: "45-90m"
+---
+
+# Workflow: Agency CRO Funnel Teardown & Onboarding Optimization
+
+## Overview & Scope
+Systematic conversion rate optimization process auditing customer signup funnels, identifying drop-off friction points, and implementing A/B split-test variants.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Funnel URL]) --> P1[Phase 1: Funnel Heuristic & DOM Audit]
+    P1 --> P2[Phase 2: Experiment Hypothesis & UI Variant Design]
+    P2 --> Gate1{"Playwright E2E Tests Pass?"}
+    Gate1 -->|Fail| P2
+    Gate1 -->|Pass| P3[Phase 3: Rollout Strategy & Tracking Gates]
+    P3 --> Done([Experiment Ready])
+```
+
+## Required Tool Inputs & Context
+- Funnel URL, conversion funnel metrics, or analytics tracking
+- Playwright MCP / test runner for automated flow simulation
+- CRO heuristics framework (Fogg Behavior Model, LIFT model)
+
+## Phase 1: Funnel Teardown & Friction Analysis
+- Inspect onboarding steps, form input fields, and social proof placement.
+- Identify friction, value clarity issues, and anxiety triggers.
+
+## Phase 2: Hypothesis & Variant Design
+- Formulate CRO hypothesis: *If we [change], then [metric] will increase because [reason]*.
+- Design high-converting variant UI components and copy.
+
+## Phase 3: Verification & Test Execution
+- Run Playwright test simulating user signup flow on variants.
+- Validate analytics event dispatching and conversion triggers.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Friction audit completed | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Variants coded & tokenized | `npm run typecheck` | UI variants compile without type errors |
+| Phase 3 -> Completion | E2E simulations green | `npm test` | Playwright test completes with 0 form drop-offs |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: All form validation messages are clear and accessible.
+- **Automated Rollback Protocol**: Revert to control funnel if form submission fails in E2E sandbox.

package/registry/workflows/workflow-agency-full-campaign.md

@@ -0,0 +1,58 @@
+---
+name: "Digital Agency Full-Funnel Campaign Orchestration"
+description: "End-to-end multi-agent cross-functional agency workflow spanning strategy, copywriting, UI/UX design, frontend development, and compliance audit."
+bundle: "digital-agency"
+estimatedDuration: "120-180m"
+---
+
+# Workflow: Digital Agency Full-Funnel Campaign Orchestration
+
+## Overview & Scope
+The Full-Funnel Campaign workflow coordinates the AstrolabsAI team roster (`chris-director`, `ava-manager`, `kaan-copy`, `jamileh-design`, `yavuz-content`, `jale-social`) through dynamic DAG message handoffs (`/handoff`, `/design-handoff-spec`) across Tri-Tier execution envelopes.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Client Brief Intake]) --> P1[Phase 1: Strategy & Intelligence / Chris & Ava]
+    P1 --> Gate1{"Strategy Signed Off?"}
+    Gate1 -->|No| P1
+    Gate1 -->|Yes| P2[Phase 2: Creative Handoff / Kaan & Jamileh]
+    P2 --> Gate2{"Design Tokens & Copy Approved?"}
+    Gate2 -->|No| P2
+    Gate2 -->|Yes| P3[Phase 3: Production & Compliance / Yavuz & QA]
+    P3 --> Gate3{"Verification Suite Green?"}
+    Gate3 -->|No| P3
+    Gate3 -->|Pass| Done([Campaign Ready for Launch])
+```
+
+## Required Tool Inputs & Context
+- Client product brief & target ICP demographics
+- Brand assets, color tokens & design systems
+- Active MCP servers (GitHub, Firecrawl, Context7, Playwright, Figma) or Fallback mode
+
+## Phase 1: Context & Strategy (Chris & Ava)
+- Ingest client brief or deck via MarkItDown / Firecrawl.
+- Formulate campaign objectives, CAC targets, and channel strategy.
+- Dispatch structured `/handoff` to creative specialists.
+
+## Phase 2: Copywriting & Visual Design (Kaan & Jamileh)
+- Author high-converting ad copy variants, email sequences, and landing page headlines.
+- Design Figma/Tailwind component layouts, Storybook preview cards, and visual assets.
+- Validate WCAG 2.2 AA accessibility contrast.
+
+## Phase 3: Frontend Implementation & Verification (Yavuz & Compliance)
+- Implement interactive responsive UI in React/Next.js.
+- Execute Playwright E2E CRO funnel tests and performance lighthouse checks.
+- Audit data privacy and advertising compliance (GDPR, CAN-SPAM).
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Strategy formulated & budget approved | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Copy & visual prototypes completed | `npm run typecheck` | Component layouts and tokens compile cleanly |
+| Phase 3 -> Completion | End-to-end integration verified | `npm test` | 100% pass across E2E test suites and accessibility gates |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Copy and creative variants pass brand voice guidelines.
+- **Validation Checkpoint 2**: Playwright funnel test confirms zero form submission drop-offs.
+- **Automated Rollback Protocol**: If API tokens or MCP servers fail, orchestrator transitions dynamically to Brainstorming/Limited mode.

package/registry/workflows/workflow-agency-seo-content-engine.md

@@ -0,0 +1,50 @@
+---
+name: "Agency Programmatic SEO & Content Pipeline"
+description: "Data-driven programmatic SEO keyword clustering, content architecture, schema markup injection, and technical audit pipeline."
+bundle: "digital-agency"
+estimatedDuration: "60-120m"
+---
+
+# Workflow: Agency Programmatic SEO & Content Pipeline
+
+## Overview & Scope
+Drives organic traffic acquisition through keyword clustering, competitor gap scraping (via Firecrawl MCP), content briefs, and structured schema markup.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Domain Scope]) --> P1[Phase 1: Keyword & Competitor Scraping]
+    P1 --> P2[Phase 2: Content Brief & Schema Authoring]
+    P2 --> Gate1{"Technical SEO Check?"}
+    Gate1 -->|Fail| P2
+    Gate1 -->|Pass| P3[Phase 3: Publishing Pipeline Verification]
+    P3 --> Done([Engine Live])
+```
+
+## Required Tool Inputs & Context
+- Seed keywords and target industry topic clusters
+- Firecrawl MCP server or local web scraping fallback
+- JSON-LD schema taxonomy
+
+## Phase 1: Keyword Research & Gap Analysis
+- Extract competitor URL maps and ranking structures.
+- Cluster search intent keywords into high-intent landing page buckets.
+
+## Phase 2: Content Briefs & JSON-LD Generation
+- Generate markdown content outlines with H1-H3 header hierarchies.
+- Author schema markup (FAQPage, Article, SoftwareApplication, Organization).
+
+## Phase 3: Verification & Auditing
+- Validate schema JSON-LD with structured data validators.
+- Inspect Core Web Vitals impact and meta tags.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Keyword clusters mapped | `node dist/cli.js doctor` | Doctor health check succeeds with 0 errors |
+| Phase 2 -> Phase 3 | Schema markup authored | `npm test` | JSON-LD syntax validation passes 100% |
+| Phase 3 -> Completion | Audit complete | `npm run build` | Zero broken references or missing meta tags |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Schema markup strictly conforms to Schema.org standards.
+- **Automated Rollback Protocol**: Strip non-standard schema tags if structured validation fails.

package/registry/workflows/workflow-analyze.md

@@ -0,0 +1,60 @@
+---
+name: "Codebase Security & Static Analysis"
+description: "Workflow for executing static code analysis, vulnerability scanning, security audits, and code health assessments."
+bundle: "security-operations"
+estimatedDuration: "30-50m"
+---
+
+# Workflow: Codebase Security & Static Analysis
+
+## Overview & Scope
+The Analyze workflow enforces codebase security hygiene. It runs static application security testing (SAST), scans for exposed secrets, audits dependency vulnerabilities, and evaluates code complexity.
+
+## 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
+- Source code repository
+- Static security scanning tools (`npm audit`, `snyk`, `semgrep`, `secret-scanner`)
+- Dependency manifest (`package.json`)
+
+## Phase 1: Context & Reconnaissance
+- Identify target source directories, configuration files, and external dependencies.
+- Configure SAST rules and vulnerability severity thresholds (Critical, High, Medium, Low).
+- Check scanning tool dependencies.
+
+## Phase 2: Execution & Orchestration
+- Execute dependency vulnerability audit (`npm audit`).
+- Run SAST scanners to detect code vulnerabilities (XSS, SQLi, path traversal, hardcoded secrets).
+- Audit code complexity metrics (cyclomatic complexity, maintainability index).
+
+## Phase 3: Verification & Closure
+- Classify findings by severity and impact.
+- Generate actionable remediation diffs for identified vulnerabilities.
+- Publish Codebase Security & Static Analysis 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 audit` | Zero Critical or High severity security vulnerabilities detected |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm run typecheck` | Static type checking passes cleanly |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Zero exposed secrets or credentials found in source code.
+- **Validation Checkpoint 2**: Security analysis report includes explicit remediation steps for all findings.
+- **Automated Rollback Protocol**: Block build deployment immediately if Critical severity security vulnerabilities are discovered.

package/registry/workflows/workflow-api-contract-design.md

@@ -0,0 +1,48 @@
+---
+name: "API Contract & Schema Design"
+description: "Workflow for designing, validating, and versioning REST OpenAPI 3.1, GraphQL, and gRPC protobuf schema contracts with zero breaking changes."
+bundle: "backend-distributed-systems"
+estimatedDuration: "15-30m"
+---
+
+# Workflow: API Contract & Schema Design
+
+## Overview & Scope
+The API Contract Design workflow ensures all client-server and microservice communications have strictly typed, backward-compatible, and documented API schemas before implementation begins.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Domain Modeling & Entity Definition]
+    P1 --> InputCheck{"Entities & Types Modeled?"}
+    InputCheck -->|No| Abort1[Clarify Domain Schema]
+    InputCheck -->|Yes| P2[Phase 2: Schema Contract Generation]
+    P2 --> Gate1{"Verification Gate: Schema Valid & Compatible?"}
+    Gate1 -->|Fail| P2Fix[Resolve Schema Incompatibilities]
+    P2Fix --> P2
+    Gate1 -->|Pass| P3[Phase 3: Client SDK & Mock Generation]
+    P3 --> Done([API Contract Approved & Published])
+```
+
+## Required Tool Inputs & Context
+- Domain entity model and service requirements
+- Target API style (`REST OpenAPI`, `GraphQL`, `gRPC Protobuf`)
+- Backward compatibility requirements
+
+## Phase 1: Domain Modeling & Entity Definition
+- Map domain models to request/response payloads, error structures, and pagination patterns.
+- Enforce standard HTTP status code and error payload conventions (`RFC 7807`).
+
+## Phase 2: Schema Contract Generation
+- Author OpenAPI YAML, GraphQL SDL, or Protobuf `.proto` definition.
+- Run schema linting (`spectral` / `buf lint`) and breaking change detection (`buf breaking` / `oasdiff`).
+
+## Phase 3: Client SDK & Mock Generation
+- Generate typed client SDKs and mock server definitions (MSW / Prism) for parallel frontend development.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Domain entities specified | Entity mapping review | All mandatory fields and types declared |
+| Phase 2 -> Phase 3 | Schema authored | Schema linter & diff tool | 0 lint errors, 0 breaking changes detected |
+| Phase 3 -> Completion | SDK & mocks generated | Mock server validation | Client SDK compiles without type errors |

package/registry/workflows/workflow-app-store-release.md

@@ -0,0 +1,48 @@
+---
+name: "App Store & Google Play Release Preparation"
+description: "Workflow for auditing mobile application compliance, privacy policy disclosures, StoreKit/In-App Purchases, and app store submission assets."
+bundle: "mobile-development"
+estimatedDuration: "20-40m"
+---
+
+# Workflow: App Store & Google Play Release Preparation
+
+## Overview & Scope
+The App Store Release workflow audits mobile applications against Apple App Review Guidelines and Google Play Developer Policies prior to store submission, eliminating common rejection causes.
+
+## Execution Flowchart
+```mermaid
+graph TD
+    Start([Start Workflow]) --> P1[Phase 1: Privacy & Entitlements Audit]
+    P1 --> InputCheck{"Info.plist & Manifest Complete?"}
+    InputCheck -->|No| Abort1[Remediate Missing Descriptions]
+    InputCheck -->|Yes| P2[Phase 2: StoreKit & Permissions Verification]
+    P2 --> Gate1{"Verification Gate: Guidelines Compliant?"}
+    Gate1 -->|Fail| P2Fix[Apply Compliance Fixes]
+    P2Fix --> P2
+    Gate1 -->|Pass| P3[Phase 3: Metadata & Release Artifact Packaging]
+    P3 --> Done([App Store Submission Ready])
+```
+
+## Required Tool Inputs & Context
+- `Info.plist` (iOS) / `AndroidManifest.xml` (Android)
+- Privacy Policy URL and Terms of Service links
+- Screenshot assets for target screen sizes
+
+## Phase 1: Privacy & Entitlements Audit
+- Verify that every requested permission (Camera, Location, Notifications) includes a clear, user-facing purpose string.
+- Audit third-party SDK privacy manifests and data collection disclosures.
+
+## Phase 2: StoreKit & Permissions Verification
+- Verify In-App Purchase restore purchase functionality and clear pricing disclosures.
+- Verify account deletion capabilities for apps with user authentication.
+
+## Phase 3: Metadata & Release Artifact Packaging
+- Compile App Store Connect / Google Play metadata, release notes, and version increment commits.
+
+## Phase Transition Criteria & Deterministic Verification Gates
+| Transition | Prerequisites | Verification Command / Gate | Success Criteria |
+|---|---|---|---|
+| Phase 1 -> Phase 2 | Permission strings verified | Manifest & Info.plist audit | 100% of requested permissions have explanations |
+| Phase 2 -> Phase 3 | Store compliance verified | Guidelines checklist audit | Account deletion & purchase restore verified |
+| Phase 3 -> Completion | Metadata bundle signed off | Release notes & version audit | Clean submission package prepared |

package/registry/workflows/workflow-brainstorm.md

@@ -0,0 +1,60 @@
+---
+name: "Structured Option Generation & Brainstorming"
+description: "Workflow for generating creative technical solutions, evaluating design options, and applying SCAMPER/Lateral Thinking frameworks."
+bundle: "deep-research"
+estimatedDuration: "25-45m"
+---
+
+# Workflow: Structured Option Generation & Brainstorming
+
+## Overview & Scope
+This workflow drives structured technical innovation. It applies SCAMPER and Lateral Thinking frameworks to generate diverse solution options before narrowing down to optimal candidates.
+
+## 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
+- Problem context statement & hard project constraints
+- Brainstorming framework guides (SCAMPER, 6 Thinking Hats)
+- Option evaluation matrix template
+
+## Phase 1: Context & Reconnaissance
+- Review target problem statement and state non-negotiable constraints (tech stack, latency budget, timeline).
+- Set target idea volume goal (minimum 10 distinct solution concepts).
+- Prepare brainstorming workspace.
+
+## Phase 2: Execution & Orchestration
+- Divergent Phase: Generate high-volume ideas using SCAMPER (Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse).
+- Categorize generated ideas into architectural clusters.
+- Convergent Phase: Evaluate ideas against feasibility, impact, and project constraints.
+
+## Phase 3: Verification & Closure
+- Select top 3 candidate options for detailed technical evaluation.
+- Document pros, cons, trade-offs, and risks for each top option.
+- Publish Technical Option Generation 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 validates brainstorming document schema |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm test` | Validation test confirms presence of top candidate trade-off analyses |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Minimum of 10 distinct solution options generated during divergent phase.
+- **Validation Checkpoint 2**: Top candidate options evaluated against all hard project constraints.
+- **Automated Rollback Protocol**: Re-frame brainstorming prompt if generated concepts violate core constraints.

package/registry/workflows/workflow-build.md

@@ -0,0 +1,60 @@
+---
+name: "Production Build Verification"
+description: "Workflow for executing production build compilation, validating bundle output integrity, asset sizes, and target artifacts."
+bundle: "software-engineering"
+estimatedDuration: "15-30m"
+---
+
+# Workflow: Production Build Verification
+
+## Overview & Scope
+The Build workflow ensures project code compiles cleanly into production-ready build artifacts, validating bundle sizes, entry point executables, and asset integrity prior to deployment.
+
+## 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
+- Build script and bundling tool (`tsup` / `vite` / `webpack` / `esbuild`)
+- Target output directory (`dist/` or `build/`)
+- Maximum allowable bundle size thresholds
+
+## Phase 1: Context & Reconnaissance
+- Inspect build tool configuration files (`tsconfig.json`, `tsup.config.ts`, `vite.config.ts`).
+- Clean prior build artifacts and temporary files (`rimraf dist`).
+- Verify all required build dependencies and environment variables are present.
+
+## Phase 2: Execution & Orchestration
+- Execute production compilation process via `npm run build`.
+- Monitor stdout/stderr streams for compilation warnings, deprecation notices, or missing exports.
+- Inspect generated output artifacts to confirm expected entry point scripts and source maps are emitted.
+
+## Phase 3: Verification & Closure
+- Run post-build asset verification scripts to check bundle file sizes against thresholds.
+- Test executable CLI entry points or bundled modules in an isolated node process.
+- Publish build verification summary detailing artifact sizes, compilation time, and entry signatures.
+
+## 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 run build` | Compilation completes with exit code 0 and zero fatal errors |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `node dist/cli.js --version` | Built CLI entry point executes cleanly without module resolution errors |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Output directory contains all expected JavaScript, type declaration (`.d.ts`), and map files.
+- **Validation Checkpoint 2**: Bundle size measurements fall within acceptable performance budget limits.
+- **Automated Rollback Protocol**: Clean corrupted `dist/` artifacts and revert build configuration changes if compilation fails.

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

@@ -0,0 +1,60 @@
+---
+name: "Expert Business Evaluation Panel"
+description: "Panel workflow assembling business strategists, product managers, and financial analysts to evaluate product monetization, pricing, and business viability."
+bundle: "business-strategy"
+estimatedDuration: "45-75m"
+---
+
+# Workflow: Expert Business Evaluation Panel
+
+## Overview & Scope
+The Business Panel workflow evaluates commercial viability. It convenes Business Strategists, Financial Analysts, and Product Managers to audit monetization models, pricing strategy, unit economics, and ROI.
+
+## 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
+- Business proposal or feature specification
+- Monetization model & pricing tier specs
+- Financial projections and market size data
+
+## Phase 1: Context & Reconnaissance
+- Gather business proposals, financial estimates, and target market analysis.
+- Establish evaluation dimensions (Monetization feasibility, Unit economics, Customer CAC/LTV, Competitive defensibility).
+- Distribute proposal to business panel personas.
+
+## Phase 2: Execution & Orchestration
+- Conduct panel review session collecting structured evaluation from business expert personas.
+- Audit pricing tiers, margin expectations, and go-to-market assumptions.
+- Identify commercial risks and strategic opportunities.
+
+## Phase 3: Verification & Closure
+- Synthesize panel feedback into Business Evaluation Verdict (Approved, Approved with Adjustments, Rejected).
+- Formulate actionable commercial recommendations and financial model updates.
+- Publish Business Panel Evaluation 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 validates business panel report format |
+| Phase 3 -> Completion | Verification complete & artifacts signed off | `npm test` | Validation test suite confirms presence of financial metrics |
+
+## Validation Checkpoints & Automated Rollback Protocols
+- **Validation Checkpoint 1**: Monetization model and unit economics evaluated across all proposed pricing tiers.
+- **Validation Checkpoint 2**: Commercial risks cataloged with explicit mitigation recommendations.
+- **Automated Rollback Protocol**: Return proposal to draft state if panel issues commercial rejection verdict.