How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

aigency_brownfield_fullstack - Prompt

Name: aigency_brownfield_fullstack
Author: AReid987

Prompt file imported from AReid987/aigency-v1.0.0 (.windsurf/workflows/aigency_brownfield_fullstack.md). Fill in {{enhancement_type}}, {{document_list}}, {{specific_changes}}, {{documentation_type}} before use. Copyright stays with the author.

Sequence

Enhancement Classification
- Agent: analyst
- Action: Classify enhancement scope
- Notes: | Determine enhancement complexity to route to appropriate path:
  - Single story (< 4 hours) → Use brownfield-create-story task
  - Small feature (1-3 stories) → Use brownfield-create-epic task
  - Major enhancement (multiple epics) → Continue with full workflow
Documentation Check
- Agent: analyst
- Action: Check existing documentation
- Condition: Major enhancement path
- Notes: | Check if adequate project documentation exists:
  - Look for existing architecture docs, API specs, coding standards
  - Assess if documentation is current and comprehensive
  - If adequate: Skip document-project, proceed to PRD
  - If inadequate: Run document-project first
Project Analysis
- Agent: architect
- Action: Analyze existing project using document-project
- Creates: brownfield-architecture.md (or multiple documents)
- Condition: Documentation inadequate
- Notes: Run document-project to capture current system state, technical debt, and constraints.
Create PRD
- Agent: pm
- Creates: prd.md
- Uses: brownfield-prd-tmpl
- Requires: Existing documentation or analysis
- Notes: | Creates PRD for major enhancement. If document-project was run, reference its output to avoid re-analysis. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.
Architecture Decision
- Agent: pm/architect
- Action: Determine if architecture document needed
- Condition: After PRD creation
- Notes: | Review PRD to determine if architectural planning is needed:
  - New architectural patterns → Create architecture doc
  - New libraries/frameworks → Create architecture doc
  - Platform/infrastructure changes → Create architecture doc
  - Following existing patterns → Skip to story creation
Create Architecture Document
- Agent: architect
- Creates: architecture.md
- Uses: brownfield-architecture-tmpl
- Requires: prd.md
- Condition: Architecture changes needed
- Notes: Creates architecture ONLY for significant architectural changes.
Artifact Validation
- Agent: po
- Validates: All artifacts
- Uses: po-master-checklist
- Notes: Validates all documents for integration safety and completeness.
Document Sharding
- Agent: po
- Action: Shard documents
- Creates: Sharded documentation
- Requires: All artifacts in project
- Notes: | Shard documents for IDE development:
  - Creates docs/prd/ and docs/architecture/ folders with sharded content
Story Creation
- Agent: sm
- Action: Create story
- Creates: story.md
- Requires: Sharded docs or brownfield docs
- Repeats: For each epic or enhancement
- Notes: | Story creation cycle:
  - For sharded PRD: Use create-next-story
  - For brownfield docs: Use create-brownfield-story task
  - Creates story from available documentation
  - Story starts in "Draft" status
Implementation
- Agent: dev
- Action: Implement story
- Creates: Implementation files
- Requires: story.md
- Notes: Implements approved story and updates file list with all changes.
QA Review
- Agent: qa
- Action: Review implementation
- Updates: Implementation files
- Optional: true
- Notes: | QA Agent reviews implementation:
  - Senior dev review with refactoring ability
  - Fixes small issues directly
  - Leaves checklist for remaining items

Flow Diagram

graph TD
    A[Start: Brownfield Enhancement] --> B[analyst: classify enhancement scope]
    B --> C{Enhancement Size?}

    C -->|Single Story| D[pm: brownfield-create-story]
    C -->|1-3 Stories| E[pm: brownfield-create-epic]
    C -->|Major Enhancement| F[analyst: check documentation]

    D --> END1[To Dev Implementation]
    E --> END2[To Story Creation]

    F --> G{Docs Adequate?}
    G -->|No| H[architect: document-project]
    G -->|Yes| I[pm: brownfield PRD]
    H --> I

    I --> J{Architecture Needed?}
    J -->|Yes| K[architect: architecture.md]
    J -->|No| L[po: validate artifacts]
    K --> L

    L --> M{PO finds issues?}
    M -->|Yes| N[Fix issues]
    M -->|No| O[po: shard documents]
    N --> L

    O --> P[sm: create story]
    P --> Q{Story Type?}
    Q -->|Sharded PRD| R[create-next-story]
    Q -->|Brownfield Docs| S[create-brownfield-story]

    R --> T{Review draft?}
    S --> T
    T -->|Yes| U[review & approve]
    T -->|No| V[dev: implement]
    U --> V

    V --> W{QA review?}
    W -->|Yes| X[qa: review]
    W -->|No| Y{More stories?}
    X --> Z{Issues?}
    Z -->|Yes| AA[dev: fix]
    Z -->|No| Y
    AA --> X
    Y -->|Yes| P
    Y -->|No| AB{Retrospective?}
    AB -->|Yes| AC[po: retrospective]
    AB -->|No| AD[Complete]
    AC --> AD

    style AD fill:#90EE90
    style END1 fill:#90EE90
    style END2 fill:#90EE90
    style D fill:#87CEEB
    style E fill:#87CEEB
    style I fill:#FFE4B5
    style K fill:#FFE4B5
    style O fill:#ADD8E6
    style P fill:#ADD8E6
    style V fill:#ADD8E6
    style U fill:#F0E68C
    style X fill:#F0E68C
    style AC fill:#F0E68C

Decision Guidance

When to Use

Enhancement requires coordinated stories
Architectural changes are needed
Significant integration work required
Risk assessment and mitigation planning necessary
Multiple team members will work on related changes

Handoff Prompts

Classification Complete

Enhancement classified as: {{enhancement_type}}
{{if single_story}}: Proceeding with brownfield-create-story task for immediate implementation.
{{if small_feature}}: Creating focused epic with brownfield-create-epic task.
{{if major_enhancement}}: Continuing with comprehensive planning workflow.

Documentation Assessment

Documentation assessment complete:
{{if adequate}}: Existing documentation is sufficient. Proceeding directly to PRD creation.
{{if inadequate}}: Running document-project to capture current system state before PRD.

Document Project to PM

Project analysis complete. Key findings documented in:
- {{document_list}}
Use these findings to inform PRD creation and avoid re-analyzing the same aspects.

PM to Architect Decision

PRD complete and saved as docs/prd.md.
Architectural changes identified: {{yes/no}}
{{if yes}}: Proceeding to create architecture document for: {{specific_changes}}
{{if no}}: No architectural changes needed. Proceeding to validation.

Architect to PO

Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety.

PO to SM

All artifacts validated.
Documentation type available: {{sharded_prd / brownfield_docs}}
{{if sharded}}: Use standard create-next-story task.
{{if brownfield}}: Use create-brownfield-story task to handle varied documentation formats.

SM Story Creation

Creating story from {{documentation_type}}.
{{if missing_context}}: May need to gather additional context from user during story creation.

Complete

All planning artifacts validated and development can begin. Stories will be created based on available documentation format.

Install aigency_brownfield_fullstack and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

## Sequence 1. **Enhancement Classification** - Agent: analyst - Action: Classify enhancement scope - Notes: | Determine enhancement complexity to route to appropriate path: - Single story (< 4 hours) → Use brownfield-create-story task - Small feature (1-3 stories) → Use brownfield-create-epic task - Major enhancement (multiple epics) → Continue with full workflow 2. **Documentation Check** - Agent: analyst - Action: Check existing documentation - Condition: Major enhancement path - Notes: | Check if adequate project documentation exists: - Look for existing architecture docs, API specs, coding standards - Assess if documentation is current and comprehensive - If adequate: Skip document-project, proceed to PRD - If inadequate: Run document-project first 3. **Project Analysis** - Agent: architect - Action: Analyze existing project using document-project - Creates: brownfield-architecture.md (or multiple documents) - Condition: Documentation inadequate - Notes: Run document-project to capture current system state, technical debt, and constraints. 4. **Create PRD** - Agent: pm - Creates: prd.md - Uses: brownfield-prd-tmpl - Requires: Existing documentation or analysis - Notes: | Creates PRD for major enhancement. If document-project was run, reference its output to avoid re-analysis. SAVE OUTPUT: Copy final prd.md to your project's docs/ folder. 5. **Architecture Decision** - Agent: pm/architect - Action: Determine if architecture document needed - Condition: After PRD creation - Notes: | Review PRD to determine if architectural planning is needed: - New architectural patterns → Create architecture doc - New libraries/frameworks → Create architecture doc - Platform/infrastructure changes → Create architecture doc - Following existing patterns → Skip to story creation 6. **Create Architecture Document** - Agent: architect - Creates: architecture.md - Uses: brownfield-architecture-tmpl - Requires: prd.md - Condition: Architecture changes needed - Notes: Creates architecture ONLY for significant architectural changes. 7. **Artifact Validation** - Agent: po - Validates: All artifacts - Uses: po-master-checklist - Notes: Validates all documents for integration safety and completeness. 8. **Document Sharding** - Agent: po - Action: Shard documents - Creates: Sharded documentation - Requires: All artifacts in project - Notes: | Shard documents for IDE development: - Creates docs/prd/ and docs/architecture/ folders with sharded content 9. **Story Creation** - Agent: sm - Action: Create story - Creates: story.md - Requires: Sharded docs or brownfield docs - Repeats: For each epic or enhancement - Notes: | Story creation cycle: - For sharded PRD: Use create-next-story - For brownfield docs: Use create-brownfield-story task - Creates story from available documentation - Story starts in "Draft" status 10. **Implementation** - Agent: dev - Action: Implement story - Creates: Implementation files - Requires: story.md - Notes: Implements approved story and updates file list with all changes. 11. **QA Review** - Agent: qa - Action: Review implementation - Updates: Implementation files - Optional: true - Notes: | QA Agent reviews implementation: - Senior dev review with refactoring ability - Fixes small issues directly - Leaves checklist for remaining items ## Flow Diagram ```mermaid graph TD A[Start: Brownfield Enhancement] --> B[analyst: classify enhancement scope] B --> C{Enhancement Size?} C -->|Single Story| D[pm: brownfield-create-story] C -->|1-3 Stories| E[pm: brownfield-create-epic] C -->|Major Enhancement| F[analyst: check documentation] D --> END1[To Dev Implementation] E --> END2[To Story Creation] F --> G{Docs Adequate?} G -->|No| H[architect: document-project] G -->|Yes| I[pm: brownfield PRD] H --> I I --> J{Architecture Needed?} J -->|Yes| K[architect: architecture.md] J -->|No| L[po: validate artifacts] K --> L L --> M{PO finds issues?} M -->|Yes| N[Fix issues] M -->|No| O[po: shard documents] N --> L O --> P[sm: create story] P --> Q{Story Type?} Q -->|Sharded PRD| R[create-next-story] Q -->|Brownfield Docs| S[create-brownfield-story] R --> T{Review draft?} S --> T T -->|Yes| U[review & approve] T -->|No| V[dev: implement] U --> V V --> W{QA review?} W -->|Yes| X[qa: review] W -->|No| Y{More stories?} X --> Z{Issues?} Z -->|Yes| AA[dev: fix] Z -->|No| Y AA --> X Y -->|Yes| P Y -->|No| AB{Retrospective?} AB -->|Yes| AC[po: retrospective] AB -->|No| AD[Complete] AC --> AD style AD fill:#90EE90 style END1 fill:#90EE90 style END2 fill:#90EE90 style D fill:#87CEEB style E fill:#87CEEB style I fill:#FFE4B5 style K fill:#FFE4B5 style O fill:#ADD8E6 style P fill:#ADD8E6 style V fill:#ADD8E6 style U fill:#F0E68C style X fill:#F0E68C style AC fill:#F0E68C ``` ## Decision Guidance ### When to Use - Enhancement requires coordinated stories - Architectural changes are needed - Significant integration work required - Risk assessment and mitigation planning necessary - Multiple team members will work on related changes ## Handoff Prompts ### Classification Complete ``` Enhancement classified as: {{enhancement_type}} {{if single_story}}: Proceeding with brownfield-create-story task for immediate implementation. {{if small_feature}}: Creating focused epic with brownfield-create-epic task. {{if major_enhancement}}: Continuing with comprehensive planning workflow. ``` ### Documentation Assessment ``` Documentation assessment complete: {{if adequate}}: Existing documentation is sufficient. Proceeding directly to PRD creation. {{if inadequate}}: Running document-project to capture current system state before PRD. ``` ### Document Project to PM ``` Project analysis complete. Key findings documented in: - {{document_list}} Use these findings to inform PRD creation and avoid re-analyzing the same aspects. ``` ### PM to Architect Decision ``` PRD complete and saved as docs/prd.md. Architectural changes identified: {{yes/no}} {{if yes}}: Proceeding to create architecture document for: {{specific_changes}} {{if no}}: No architectural changes needed. Proceeding to validation. ``` ### Architect to PO ``` Architecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety. ``` ### PO to SM ``` All artifacts validated. Documentation type available: {{sharded_prd / brownfield_docs}} {{if sharded}}: Use standard create-next-story task. {{if brownfield}}: Use create-brownfield-story task to handle varied documentation formats. ``` ### SM Story Creation ``` Creating story from {{documentation_type}}. {{if missing_context}}: May need to gather additional context from user during story creation. ``` ### Complete ``` All planning artifacts validated and development can begin. Stories will be created based on available documentation format. ```

{ "prompt": "## Sequence\n\n1. **Enhancement Classification**\n - Agent: analyst\n - Action: Classify enhancement scope\n - Notes: |\n Determine enhancement complexity to route to appropriate path:\n - Single story (< 4 hours) → Use brownfield-create-story task\n - Small feature (1-3 stories) → Use brownfield-create-epic task\n - Major enhancement (multiple epics) → Continue with full workflow\n\n2. **Documentation Check**\n - Agent: analyst\n - Action: Check existing documentation\n - Condition: Major enhancement path\n - Notes: |\n Check if adequate project documentation exists:\n - Look for existing architecture docs, API specs, coding standards\n - Assess if documentation is current and comprehensive\n - If adequate: Skip document-project, proceed to PRD\n - If inadequate: Run document-project first\n\n3. **Project Analysis**\n - Agent: architect\n - Action: Analyze existing project using document-project\n - Creates: brownfield-architecture.md (or multiple documents)\n - Condition: Documentation inadequate\n - Notes: Run document-project to capture current system state, technical debt, and constraints.\n\n4. **Create PRD**\n - Agent: pm\n - Creates: prd.md\n - Uses: brownfield-prd-tmpl\n - Requires: Existing documentation or analysis\n - Notes: |\n Creates PRD for major enhancement. If document-project was run, reference its output to avoid re-analysis.\n SAVE OUTPUT: Copy final prd.md to your project's docs/ folder.\n\n5. **Architecture Decision**\n - Agent: pm/architect\n - Action: Determine if architecture document needed\n - Condition: After PRD creation\n - Notes: |\n Review PRD to determine if architectural planning is needed:\n - New architectural patterns → Create architecture doc\n - New libraries/frameworks → Create architecture doc\n - Platform/infrastructure changes → Create architecture doc\n - Following existing patterns → Skip to story creation\n\n6. **Create Architecture Document**\n - Agent: architect\n - Creates: architecture.md\n - Uses: brownfield-architecture-tmpl\n - Requires: prd.md\n - Condition: Architecture changes needed\n - Notes: Creates architecture ONLY for significant architectural changes.\n\n7. **Artifact Validation**\n - Agent: po\n - Validates: All artifacts\n - Uses: po-master-checklist\n - Notes: Validates all documents for integration safety and completeness.\n\n8. **Document Sharding**\n - Agent: po\n - Action: Shard documents\n - Creates: Sharded documentation\n - Requires: All artifacts in project\n - Notes: |\n Shard documents for IDE development:\n - Creates docs/prd/ and docs/architecture/ folders with sharded content\n\n9. **Story Creation**\n - Agent: sm\n - Action: Create story\n - Creates: story.md\n - Requires: Sharded docs or brownfield docs\n - Repeats: For each epic or enhancement\n - Notes: |\n Story creation cycle:\n - For sharded PRD: Use create-next-story\n - For brownfield docs: Use create-brownfield-story task\n - Creates story from available documentation\n - Story starts in \"Draft\" status\n\n10. **Implementation**\n - Agent: dev\n - Action: Implement story\n - Creates: Implementation files\n - Requires: story.md\n - Notes: Implements approved story and updates file list with all changes.\n\n11. **QA Review**\n - Agent: qa\n - Action: Review implementation\n - Updates: Implementation files\n - Optional: true\n - Notes: |\n QA Agent reviews implementation:\n - Senior dev review with refactoring ability\n - Fixes small issues directly\n - Leaves checklist for remaining items\n\n## Flow Diagram\n\n```mermaid\ngraph TD\n A[Start: Brownfield Enhancement] --> B[analyst: classify enhancement scope]\n B --> C{Enhancement Size?}\n\n C -->|Single Story| D[pm: brownfield-create-story]\n C -->|1-3 Stories| E[pm: brownfield-create-epic]\n C -->|Major Enhancement| F[analyst: check documentation]\n\n D --> END1[To Dev Implementation]\n E --> END2[To Story Creation]\n\n F --> G{Docs Adequate?}\n G -->|No| H[architect: document-project]\n G -->|Yes| I[pm: brownfield PRD]\n H --> I\n\n I --> J{Architecture Needed?}\n J -->|Yes| K[architect: architecture.md]\n J -->|No| L[po: validate artifacts]\n K --> L\n\n L --> M{PO finds issues?}\n M -->|Yes| N[Fix issues]\n M -->|No| O[po: shard documents]\n N --> L\n\n O --> P[sm: create story]\n P --> Q{Story Type?}\n Q -->|Sharded PRD| R[create-next-story]\n Q -->|Brownfield Docs| S[create-brownfield-story]\n\n R --> T{Review draft?}\n S --> T\n T -->|Yes| U[review & approve]\n T -->|No| V[dev: implement]\n U --> V\n\n V --> W{QA review?}\n W -->|Yes| X[qa: review]\n W -->|No| Y{More stories?}\n X --> Z{Issues?}\n Z -->|Yes| AA[dev: fix]\n Z -->|No| Y\n AA --> X\n Y -->|Yes| P\n Y -->|No| AB{Retrospective?}\n AB -->|Yes| AC[po: retrospective]\n AB -->|No| AD[Complete]\n AC --> AD\n\n style AD fill:#90EE90\n style END1 fill:#90EE90\n style END2 fill:#90EE90\n style D fill:#87CEEB\n style E fill:#87CEEB\n style I fill:#FFE4B5\n style K fill:#FFE4B5\n style O fill:#ADD8E6\n style P fill:#ADD8E6\n style V fill:#ADD8E6\n style U fill:#F0E68C\n style X fill:#F0E68C\n style AC fill:#F0E68C\n```\n\n## Decision Guidance\n\n### When to Use\n- Enhancement requires coordinated stories\n- Architectural changes are needed\n- Significant integration work required\n- Risk assessment and mitigation planning necessary\n- Multiple team members will work on related changes\n\n## Handoff Prompts\n\n### Classification Complete\n```\nEnhancement classified as: {{enhancement_type}}\n{{if single_story}}: Proceeding with brownfield-create-story task for immediate implementation.\n{{if small_feature}}: Creating focused epic with brownfield-create-epic task.\n{{if major_enhancement}}: Continuing with comprehensive planning workflow.\n```\n\n### Documentation Assessment\n```\nDocumentation assessment complete:\n{{if adequate}}: Existing documentation is sufficient. Proceeding directly to PRD creation.\n{{if inadequate}}: Running document-project to capture current system state before PRD.\n```\n\n### Document Project to PM\n```\nProject analysis complete. Key findings documented in:\n- {{document_list}}\nUse these findings to inform PRD creation and avoid re-analyzing the same aspects.\n```\n\n### PM to Architect Decision\n```\nPRD complete and saved as docs/prd.md.\nArchitectural changes identified: {{yes/no}}\n{{if yes}}: Proceeding to create architecture document for: {{specific_changes}}\n{{if no}}: No architectural changes needed. Proceeding to validation.\n```\n\n### Architect to PO\n```\nArchitecture complete. Save it as docs/architecture.md. Please validate all artifacts for integration safety.\n```\n\n### PO to SM\n```\nAll artifacts validated.\nDocumentation type available: {{sharded_prd / brownfield_docs}}\n{{if sharded}}: Use standard create-next-story task.\n{{if brownfield}}: Use create-brownfield-story task to handle varied documentation formats.\n```\n\n### SM Story Creation\n```\nCreating story from {{documentation_type}}.\n{{if missing_context}}: May need to gather additional context from user during story creation.\n```\n\n### Complete\n```\nAll planning artifacts validated and development can begin. Stories will be created based on available documentation format.\n```", "variables": [ "enhancement_type", "document_list", "specific_changes", "documentation_type" ], "notes": "Agent workflow for enhancing existing full-stack applications with new features, modernization, or significant changes. Handles existing system analysis and safe integration.", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/AReid987/aigency-v1.0.0", "path": ".windsurf/workflows/aigency_brownfield_fullstack.md", "ref": "1e93e6e5a62960362c70c89d7cd97556907f4c41", "url": "https://github.com/AReid987/aigency-v1.0.0/blob/1e93e6e5a62960362c70c89d7cd97556907f4c41/.windsurf/workflows/aigency_brownfield_fullstack.md", "key": "AReid987/aigency-v1.0.0/.windsurf/workflows/aigency_brownfield_fullstack.md" } } }

aigency_brownfield_fullstack

About

Sequence

Flow Diagram

Decision Guidance

When to Use

Handoff Prompts

Classification Complete

Documentation Assessment

Document Project to PM

PM to Architect Decision

Architect to PO

PO to SM

SM Story Creation

Complete

Install aigency_brownfield_fullstack and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews