@codemcp/workflows 6.0.1 → 6.0.2

package/packages/cli/resources/workflows/sdd-greenfield-crowd.yaml

@@ -0,0 +1,336 @@
+# yaml-language-server: $schema=../../state-machine-schema.json
+---
+name: 'sdd-greenfield-crowd'
+description: 'Collaborative greenfield project development: Team establishes constitution → Business Analyst specifies → Architect plans → Developer implements → Team documents'
+initial_state: 'constitution'
+
+# Enhanced metadata for better discoverability
+metadata:
+  domain: 'sdd-crowd'
+  complexity: 'high'
+  collaboration: true
+  requiredRoles:
+    - business-analyst
+    - architect
+    - developer
+  bestFor:
+    - 'Team-based new projects from scratch'
+    - 'Collaborative greenfield development'
+    - 'Complex system design with specialized roles'
+  useCases:
+    - 'Team builds new application from scratch'
+    - 'Collaborative creation of new service'
+  examples:
+    - 'Team builds new web application'
+    - 'Collaborative microservice architecture creation'
+
+# States with default instructions and role-specific transitions
+states:
+  constitution:
+    description: 'Establish constitutional framework and project governance'
+    default_instructions: |
+      **Team Collaboration Mode**
+
+      You are `$VIBE_ROLE` working in a collaborative team starting a new project.
+
+      All team members collaborate on establishing project principles.
+
+    transitions:
+      # All agents participate in constitution (no single responsible agent)
+      # Architect typically leads this as it's about technical governance
+      - trigger: 'constitution_established'
+        to: 'specify'
+        role: architect
+        transition_reason: 'Constitutional framework established, moving to specification'
+        additional_instructions: |
+          **STEP 1: Lead the constitutional framework**
+
+          Work with the full team to establish core principles.
+
+          **STEP 2: Create constitutional documentation**
+
+          - Create `constitution.md` in project root
+          - Define core principles for the project
+          - Establish quality gates and governance
+
+          **STEP 3: Collaborate with team members**
+
+          - Send message to business-analyst: "What are the key business principles?"
+          - Send message to developer: "What are essential development practices?"
+          - Build consensus on project values
+
+          **STEP 4: Document template sections**
+
+          - Core Principles (Specifications First, User Value, Simplicity, etc.)
+          - Quality Gates
+          - Governance
+
+          **STEP 5: Hand off to Business-Analyst**
+
+          - Send message to business-analyst: "Constitution established. Please take the lead for specification phase."
+          - Send message to developer: "Constitution ready, specification will begin next"
+          - Send message to operator: "Constitution complete, handing off to business-analyst"
+          - Call `proceed_to_phase`
+
+      - trigger: 'constitution_established'
+        to: 'specify'
+        role: business-analyst
+        transition_reason: 'Constitutional framework established, preparing to specify'
+        additional_instructions: |
+          **Contribute to the constitutional framework**
+
+          Work with architect to establish project principles.
+
+          **Business value contributions:**
+
+          - Provide input on business values and user-centric principles
+          - Suggest quality standards for specifications
+          - Define what "done" means from business perspective
+
+          **Next phase:**
+
+          - When constitution is complete, you become RESPONSIBLE
+          - You will take the lead in specify phase
+          - Prepare to create the feature specification
+
+      - trigger: 'constitution_established'
+        to: 'specify'
+        role: developer
+        transition_reason: 'Constitutional framework established, transitioning to specification'
+        additional_instructions: |
+          **Contribute to the constitutional framework**
+
+          Work with architect to establish project principles.
+
+          **Development contributions:**
+
+          - Provide input on code quality and maintainability principles
+          - Suggest development and testing practices
+          - Share experience with what works in practice
+
+  specify:
+    description: 'Create comprehensive feature specification'
+    default_instructions: |
+      **Team Collaboration Mode**
+
+      You are `$VIBE_ROLE` working in a collaborative team on this new project.
+
+      Business-analyst is responsible. Architect and developer are consulted.
+
+    transitions:
+      # Business Analyst is RESPONSIBLE for specify phase
+      - trigger: 'specification_complete'
+        to: 'plan'
+        role: business-analyst
+        transition_reason: 'Feature specification completed, handing off to architect'
+        additional_instructions: |
+          **Lead the specification phase**
+
+          Create the project specification following greenfield specification process.
+
+          **Handoff to Architect:**
+
+          - Send message to architect: "Specification complete. Please take the lead for plan phase."
+          - Send message to operator: "Specification complete, handing off to architect"
+          - Call `proceed_to_phase`
+
+      - trigger: 'specification_complete'
+        to: 'plan'
+        role: architect
+        transition_reason: 'Specification completed, preparing to plan'
+        additional_instructions: |
+          **Provide input during specification phase**
+
+          **Next phase:**
+
+          - When complete, you become RESPONSIBLE in plan phase
+
+      - trigger: 'specification_complete'
+        to: 'plan'
+        role: developer
+        transition_reason: 'Specification completed, architect will plan'
+        additional_instructions: |
+          **Provide input during specification phase**
+
+  plan:
+    description: 'Generate implementation plan with constitutional compliance'
+    default_instructions: |
+      **Team Collaboration Mode**
+
+      You are `$VIBE_ROLE` working in a collaborative team on this new project.
+
+      Architect is responsible for technology decisions and architecture.
+
+    transitions:
+      - trigger: 'plan_complete'
+        to: 'tasks'
+        role: architect
+        transition_reason: 'Implementation plan completed, moving to tasks'
+        additional_instructions: |
+          **Lead the planning phase**
+
+          **Execute planning activities:**
+
+          - Select technology stack (ask user for preferences)
+          - Design architecture
+          - Check constitutional compliance
+          - Document high-level design
+
+          **Continue in next phase:**
+
+          - You remain RESPONSIBLE in tasks phase
+
+      - trigger: 'plan_complete'
+        to: 'tasks'
+        role: business-analyst
+        transition_reason: 'Plan completed, architect moving to tasks'
+        additional_instructions: |
+          **Provide input during planning phase**
+
+      - trigger: 'plan_complete'
+        to: 'tasks'
+        role: developer
+        transition_reason: 'Plan completed, architect moving to tasks'
+        additional_instructions: |
+          **Provide input during planning phase**
+
+  tasks:
+    description: 'Generate actionable, dependency-ordered tasks'
+    default_instructions: |
+      **Team Collaboration Mode**
+
+      You are `$VIBE_ROLE` working in a collaborative team on this new project.
+
+      Architect creates task breakdown.
+
+    transitions:
+      - trigger: 'tasks_generated'
+        to: 'implement'
+        role: architect
+        transition_reason: 'Tasks generated, handing off to developer'
+        additional_instructions: |
+          **Lead the tasks phase**
+
+          Generate comprehensive task breakdown organized by user stories.
+
+          **Handoff to Developer:**
+
+          - Send handoff messages to developer
+
+      - trigger: 'tasks_generated'
+        to: 'implement'
+        role: developer
+        transition_reason: 'Tasks generated, preparing to implement'
+        additional_instructions: |
+          **Provide input during tasks phase**
+
+          **Next phase:**
+
+          - You become RESPONSIBLE in implement phase
+
+      - trigger: 'tasks_generated'
+        to: 'implement'
+        role: business-analyst
+        transition_reason: 'Tasks generated, developer will implement'
+        additional_instructions: |
+          **Receive notification during tasks phase**
+
+  implement:
+    description: 'Execute implementation following task breakdown'
+    default_instructions: |
+      **Team Collaboration Mode**
+
+      You are `$VIBE_ROLE` working in a collaborative team on this new project.
+
+      Developer drives implementation.
+
+    transitions:
+      - trigger: 'implementation_complete'
+        to: 'document'
+        role: developer
+        transition_reason: 'Implementation complete, team will document'
+        additional_instructions: |
+          **Lead the implementation phase**
+
+          Execute implementation following task breakdown.
+
+          **Handoff to Team Documentation:**
+
+          - All team members contribute to documentation phase
+
+      - trigger: 'implementation_complete'
+        to: 'document'
+        role: architect
+        transition_reason: 'Implementation complete, moving to documentation'
+        additional_instructions: |
+          **Provide input during implementation phase**
+
+      - trigger: 'implementation_complete'
+        to: 'document'
+        role: business-analyst
+        transition_reason: 'Implementation complete, moving to documentation'
+        additional_instructions: |
+          **Provide input during implementation phase**
+
+  document:
+    description: 'Create comprehensive project documentation'
+    default_instructions: |
+      **Team Collaboration Mode**
+
+      You are `$VIBE_ROLE` working in a collaborative team on this new project.
+
+      All team members contribute to documentation.
+
+    transitions:
+      - trigger: 'documentation_complete'
+        to: 'document'
+        role: developer
+        transition_reason: 'Documentation complete, project ready'
+        additional_instructions: |
+          **Finalize documentation**
+
+          Coordinate with team to create:
+
+          - User documentation
+          - Developer documentation
+          - Project documentation (README, changelog, etc.)
+
+          **Collaborate with team:**
+
+          - Business-analyst creates user guides
+          - Architect creates architecture documentation
+          - You create developer setup guides
+
+      - trigger: 'documentation_complete'
+        to: 'document'
+        role: architect
+        transition_reason: 'Documentation complete'
+        additional_instructions: |
+          **Contribute architecture documentation**
+
+          Create:
+
+          - Architecture overview
+          - Deployment guide
+          - Technical documentation
+
+      - trigger: 'documentation_complete'
+        to: 'document'
+        role: business-analyst
+        transition_reason: 'Documentation complete'
+        additional_instructions: |
+          **Contribute user documentation**
+
+          Create:
+
+          - User manual
+          - Examples
+          - User-focused guides
+
+# Global transitions
+global_transitions:
+  - trigger: 'abandon_project'
+    to: 'constitution'
+    transition_reason: 'Project abandoned, restart from beginning'
+    additional_instructions: |
+      Project abandoned. If you want to restart, begin again with establishing the constitutional framework.