speccrew 0.6.69 → 0.7.0

package/.speccrew/skills/speccrew-pm-requirement-simple/workflow.agentflow.xml

@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="requirement-simple-main" status="pending" version="1.0" desc="Simple requirement analysis for lightweight changes">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="iteration_path" required="true" type="string" desc="Path to iteration directory"/>
+    <field name="clarification_file" required="false" type="string" desc="Path to clarification summary (default: {iteration_path}/01.product-requirement/.clarification-summary.md)"/>
+    <field name="feature_name" required="true" type="string" desc="Feature name for PRD file naming"/>
+    <field name="language" required="true" type="string" desc="Language code for generated content"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="mandatory" desc="Execution constraints">
+    <field name="text">Verify .clarification-summary.md exists before proceeding</field>
+    <field name="text">Keep PRD concise - 1-3 page PRDs</field>
+    <field name="text">Use business language throughout</field>
+    <field name="text">Extract key decisions from clarification summary into PRD</field>
+  </block>
+
+  <block type="rule" id="R2" level="forbidden" desc="Content boundary constraints">
+    <field name="text">DO NOT include: API endpoint definitions, HTTP methods, request/response JSON</field>
+    <field name="text">DO NOT include: Design class diagrams, component diagrams, deployment diagrams</field>
+    <field name="text">DO NOT include: Database table structures, ER diagrams, SQL queries</field>
+    <field name="text">DO NOT include: Code snippets, pseudocode, implementation logic</field>
+    <field name="text">DO NOT include: Technical terminology (UUID, JWT, REST, Microservice, JSON)</field>
+    <field name="text">Required: Use business language only</field>
+  </block>
+
+  <block type="rule" id="R3" level="forbidden" desc="Workflow constraints">
+    <field name="text">Proceed without .clarification-summary.md</field>
+    <field name="text">Generate Master-Sub PRD structure</field>
+    <field name="text">Dispatch worker agents</field>
+    <field name="text">Wait for user confirmation (handled by PM Agent)</field>
+    <field name="text">Auto-transition to Feature Design stage</field>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="Simple PRD Generation" status="pending" desc="Generate concise PRD for simple requirements">
+
+    <!-- Step 1: Read Clarification Summary -->
+    <block type="task" id="B1" action="read-file" desc="Read clarification summary">
+      <field name="path" value="${clarification_file}"/>
+      <field name="output" var="clarification_content"/>
+    </block>
+
+    <!-- Gateway: Validate prerequisite -->
+    <block type="gateway" id="G1" mode="guard" desc="Verify clarification file exists"
+           test="${clarification_content} != null"
+           fail-action="stop">
+      <field name="message">ERROR: .clarification-summary.md not found. Run speccrew-pm-requirement-clarify first.</field>
+    </block>
+
+    <!-- Verify complexity -->
+    <block type="gateway" id="G2" mode="guard" desc="Verify simple complexity"
+           test="${clarification_content.complexity} == 'simple'"
+           fail-action="stop">
+      <field name="message">Complexity is not 'simple'. Redirect to speccrew-pm-requirement-analysis for complex requirements.</field>
+    </block>
+
+    <!-- Step 2: Read PRD Template -->
+    <block type="task" id="B2" action="run-script" desc="Search for PRD template">
+      <field name="command">Get-ChildItem -Path "." -Recurse -Filter "PRD-TEMPLATE.md" | Where-Object { $_.FullName -like "*speccrew-pm-requirement-analysis*" } | Select-Object -First 1 -ExpandProperty FullName</field>
+      <field name="output" var="template_path"/>
+    </block>
+
+    <block type="task" id="B3" action="read-file" desc="Read PRD template">
+      <field name="path" value="${template_path}"/>
+      <field name="output" var="template_content"/>
+    </block>
+
+    <!-- Step 3: Generate Single PRD -->
+    <block type="task" id="B4" action="generate" desc="Generate single PRD">
+      <field name="template" value="${template_content}"/>
+      <field name="output_path" value="${iteration_path}/01.product-requirement/${feature_name}-prd.md"/>
+      <field name="fill_sections">
+        - Section 1: Background & Goals (2-3 sentences)
+        - Section 1.2: Domain Boundary (in-scope/out-of-scope)
+        - Section 1.3/1.4: Glossary (only if new terms)
+        - Section 2: User Stories (1-3 stories)
+        - Section 3: Functional Requirements (brief description)
+        - Section 3.3: Feature List (simple table, 1-5 rows)
+        - Section 3.4: Feature Breakdown (1-5 features, all P0)
+        - Section 4: Non-Functional Requirements (if relevant)
+        - Section 5: Acceptance Criteria (3-5 criteria)
+        - Section 6: Boundary (clear in/out scope)
+        - Section 7: Assumptions (if any)
+      </field>
+      <field name="use_business_language_only">true</field>
+      <field name="data">
+        clarification: ${clarification_content}
+      </field>
+      <field name="output" var="prd_path"/>
+    </block>
+
+    <!-- Checkpoint: PRD generated -->
+    <block type="checkpoint" id="CP1" name="prd-generated" desc="Verify PRD created">
+      <field name="file" value="${prd_path}"/>
+      <field name="verify" value="file_exists(${prd_path})"/>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="prd_path" from="${prd_path}" type="string" desc="Path to generated PRD"/>
+    <field name="feature_name" from="${feature_name}" type="string" desc="Feature name"/>
+    <field name="scope" from="${clarification_content.scope}" type="string" desc="Brief scope from clarification"/>
+    <field name="complexity" value="simple" type="string" desc="Complexity level"/>
+    <field name="message" value="Simple PRD generation completed" type="string" desc="Status message"/>
+  </block>
+
+</workflow>

package/.speccrew/skills/speccrew-pm-sub-prd-generate/SKILL.md

@@ -51,7 +51,13 @@ tools: Read, Write, Glob, Grep
 1. **FORBIDDEN: Full-file rewrite** — NEVER replace the entire document content in a single operation. Always use targeted `search_replace` on specific sections.
 2. **MANDATORY: Template-first workflow** — Copy template MUST execute before filling sections.
 
-# Workflow
+# AgentFlow Definition
+
+<!-- @agentflow: workflow.agentflow.xml -->
+
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
+
+---
 
 ## Step 1: Load Context
 

package/.speccrew/skills/speccrew-pm-sub-prd-generate/workflow.agentflow.xml

@@ -0,0 +1,218 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="sub-prd-generate-main" status="pending" version="1.0" desc="Generate a single Sub-PRD document for one module">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="module_id" required="true" type="string" desc="Module ID for feature registry (e.g., M1, M2)"/>
+    <field name="module_name" required="true" type="string" desc="Human-readable module name (e.g., Customer Management)"/>
+    <field name="module_key" required="true" type="string" desc="Module identifier for file naming (e.g., customer)"/>
+    <field name="module_scope" required="true" type="string" desc="What this module covers"/>
+    <field name="module_entities" required="true" type="array" desc="Core business entities in this module"/>
+    <field name="module_user_stories" required="true" type="array" desc="User stories specific to this module"/>
+    <field name="module_requirements" required="true" type="array" desc="Functional requirements for this module (P0/P1/P2)"/>
+    <field name="module_features" required="true" type="array" desc="Feature Breakdown entries for this module"/>
+    <field name="module_dependencies" required="false" type="array" desc="Dependencies on other modules"/>
+    <field name="master_prd_path" required="true" type="string" desc="Path to the Master PRD (for cross-referencing)"/>
+    <field name="feature_name" required="true" type="string" desc="System-level feature name (for file naming prefix)"/>
+    <field name="template_path" required="true" type="string" desc="Path to PRD-TEMPLATE.md"/>
+    <field name="output_path" required="true" type="string" desc="Full path for the Sub-PRD output file"/>
+    <field name="language" required="true" type="string" desc="Language code for generated content"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="forbidden" desc="Content boundary constraints">
+    <field name="text">NO API endpoint definitions, HTTP methods, request/response JSON</field>
+    <field name="text">NO Database table structures, ER diagrams, SQL queries</field>
+    <field name="text">NO Design class diagrams, component diagrams, deployment diagrams</field>
+    <field name="text">NO Code snippets, pseudocode, implementation logic</field>
+    <field name="text">NO Technical terminology (UUID, JWT, REST, Microservice, JSON)</field>
+    <field name="text">Required: Use BUSINESS LANGUAGE ONLY</field>
+  </block>
+
+  <block type="rule" id="R2" level="forbidden" desc="Document generation constraints">
+    <field name="text">FORBIDDEN: Full-file rewrite - NEVER replace entire document content</field>
+    <field name="text">MANDATORY: Template-first workflow - Copy template before filling sections</field>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="Sub-PRD Generation" status="pending" desc="Generate Sub-PRD for a single module">
+
+    <!-- Step 1: Load Context -->
+    <block type="task" id="B1" action="read-file" desc="Read Master PRD">
+      <field name="path" value="${master_prd_path}"/>
+      <field name="output" var="master_prd_content"/>
+    </block>
+
+    <block type="task" id="B2" action="read-file" desc="Read PRD template">
+      <field name="path" value="${template_path}"/>
+      <field name="output" var="template_content"/>
+    </block>
+
+    <!-- Step 2: Create Sub-PRD File -->
+    <block type="task" id="B3" action="write-file" desc="Copy template to output path">
+      <field name="path" value="${output_path}"/>
+      <field name="content" value="${template_content}"/>
+      <field name="replace_title" from="# PRD - [Feature Name]" to="# Sub-PRD - ${module_name}"/>
+      <field name="output" var="sub_prd_created"/>
+    </block>
+
+    <!-- Step 3: Phase A - Skeleton Construction -->
+    <block type="task" id="B4" action="analyze" desc="Phase A: Build skeleton for all features">
+      <field name="input" value="${module_features}"/>
+      <field name="for_each_feature">
+        - Create #### Feature N: {feature_name}
+        - Add 6 sub-section headers:
+          * Requirement Description: [TO BE FILLED]
+          * Interaction Flow: [TO BE FILLED]
+          * Boundary Conditions: [TO BE FILLED]
+          * Exception Scenarios: [TO BE FILLED]
+          * Operation Flow Diagram: [TO BE FILLED]
+          * Operation Steps Detail: [TO BE FILLED]
+      </field>
+      <field name="output" var="skeleton_built"/>
+    </block>
+
+    <!-- Gateway: Verify skeleton complete -->
+    <block type="gateway" id="G1" mode="guard" desc="Verify all features have skeleton"
+           test="${skeleton_built.complete} == true"
+           fail-action="stop">
+      <field name="message">Skeleton construction incomplete. All features must have all 6 sub-sections.</field>
+    </block>
+
+    <!-- Step 4: Phase B - Content Filling -->
+    <block type="loop" id="L1" over="${module_features}" as="feature" desc="Fill content for each feature">
+      <block type="task" id="B5" action="search_replace" desc="Fill Requirement Description">
+        <field name="path" value="${output_path}"/>
+        <field name="replace">[TO BE FILLED] in Requirement Description section for ${feature.name}</field>
+        <field name="with">Business requirements in business language</field>
+      </block>
+
+      <block type="task" id="B6" action="search_replace" desc="Fill Interaction Flow">
+        <field name="path" value="${output_path}"/>
+        <field name="replace">[TO BE FILLED] in Interaction Flow section for ${feature.name}</field>
+        <field name="with">User interaction steps (numbered list)</field>
+      </block>
+
+      <block type="task" id="B7" action="search_replace" desc="Fill Boundary Conditions">
+        <field name="path" value="${output_path}"/>
+        <field name="replace">[TO BE FILLED] in Boundary Conditions section for ${feature.name}</field>
+        <field name="with">Table: Condition Type | Scenario | Handling Rule</field>
+      </block>
+
+      <block type="task" id="B8" action="search_replace" desc="Fill Exception Scenarios">
+        <field name="path" value="${output_path}"/>
+        <field name="replace">[TO BE FILLED] in Exception Scenarios section for ${feature.name}</field>
+        <field name="with">Bullet list of exception handling</field>
+      </block>
+
+      <block type="task" id="B9" action="search_replace" desc="Fill Operation Flow Diagram">
+        <field name="path" value="${output_path}"/>
+        <field name="replace">[TO BE FILLED] in Operation Flow Diagram section for ${feature.name}</field>
+        <field name="with">Mermaid graph LR diagram showing operation flow</field>
+      </block>
+
+      <block type="task" id="B10" action="search_replace" desc="Fill Operation Steps Detail">
+        <field name="path" value="${output_path}"/>
+        <field name="replace">[TO BE FILLED] in Operation Steps Detail section for ${feature.name}</field>
+        <field name="with">Table: Step | Action | Expected Outcome | Exception Handling</field>
+      </block>
+    </block>
+
+    <!-- Step 5: Fill remaining sections -->
+    <block type="task" id="B11" action="search_replace" desc="Fill Section 1: Background & Goals">
+      <field name="path" value="${output_path}"/>
+      <field name="sections">
+        - 1.1 Background: Why this module exists
+        - 1.2 Goals: Module-specific business objectives
+      </field>
+    </block>
+
+    <block type="task" id="B12" action="search_replace" desc="Fill Section 2: User Stories">
+      <field name="path" value="${output_path}"/>
+      <field name="sections">
+        - 2.1 Target Users
+        - 2.2 User Scenarios in As a/I want/So that format
+      </field>
+    </block>
+
+    <block type="task" id="B13" action="search_replace" desc="Fill Section 3: Functional Requirements">
+      <field name="path" value="${output_path}"/>
+      <field name="sections">
+        - 3.1 Use Case Diagram (Mermaid flowchart TB)
+        - 3.2 Business Process Flow
+        - 3.3 Feature List with P0/P1/P2
+        - 3.4 Feature Breakdown (REQUIRED)
+        - 3.5 Feature Details (all 6 sub-sections per feature)
+      </field>
+    </block>
+
+    <block type="task" id="B14" action="search_replace" desc="Fill remaining sections">
+      <field name="path" value="${output_path}"/>
+      <field name="sections">
+        - Section 4: Non-functional Requirements
+        - Section 5: Acceptance Criteria
+        - Section 6: Boundary Description
+        - Section 7: Assumptions & Dependencies
+      </field>
+    </block>
+
+    <!-- Step 6: Verify Output -->
+    <block type="task" id="B15" action="read-file" desc="Verify generated Sub-PRD">
+      <field name="path" value="${output_path}"/>
+      <field name="output" var="sub_prd_content"/>
+    </block>
+
+    <block type="gateway" id="G2" mode="guard" desc="Verify Sub-PRD is valid"
+           test="${sub_prd_content.length} > 3000 AND ${sub_prd_content} contains 'Feature Breakdown'"
+           fail-action="stop">
+      <field name="message">Sub-PRD verification failed: File too small or missing Feature Breakdown</field>
+    </block>
+
+    <!-- Step 7: Write Module Features to Feature List -->
+    <block type="task" id="B16" action="analyze" desc="Build feature list entry">
+      <field name="feature_list_path" value="dirname(${output_path})/.prd-feature-list.json"/>
+      <field name="build_entry">
+        module_id: ${module_id}
+        module_name: ${module_name}
+        module_key: ${module_key}
+        source_prd: ${feature_name}-sub-${module_key}.md
+        feature_count: ${module_features.length}
+        features: ${module_features}
+      </field>
+      <field name="output" var="feature_list_entry"/>
+    </block>
+
+    <block type="task" id="B17" action="write-file" desc="Update feature list file">
+      <field name="path" value="${feature_list_path}"/>
+      <field name="merge">true</field>
+      <field name="entry" value="${feature_list_entry}"/>
+      <field name="output" var="feature_list_updated"/>
+    </block>
+
+    <!-- Checkpoint: Sub-PRD complete -->
+    <block type="checkpoint" id="CP1" name="sub-prd-complete" desc="Verify Sub-PRD generation completed">
+      <field name="file" value="${output_path}"/>
+      <field name="verify" value="file_exists(${output_path})"/>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="sub_prd_path" from="${output_path}" type="string" desc="Path to generated Sub-PRD"/>
+    <field name="module_id" from="${module_id}" type="string" desc="Module ID"/>
+    <field name="module_name" from="${module_name}" type="string" desc="Module name"/>
+    <field name="feature_count" from="${module_features.length}" type="number" desc="Number of features"/>
+    <field name="feature_list_updated" from="${feature_list_updated}" type="boolean" desc="Whether feature list was updated"/>
+    <field name="message" value="Sub-PRD generation completed" type="string" desc="Status message"/>
+  </block>
+
+</workflow>

package/.speccrew/skills/speccrew-sd-backend/SKILL.md

@@ -10,7 +10,13 @@ tools: Read, Write, Glob, Grep
 - System Designer Agent receives task to create backend detailed design for a specific platform
 - User asks "Design backend implementation" or "Create backend design for {platform}"
 
-# Workflow
+## AgentFlow Definition
+
+<!-- @agentflow: workflow.agentflow.xml -->
+
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
+
+## Workflow
 
 ## Absolute Constraints
 

package/.speccrew/skills/speccrew-sd-backend/workflow.agentflow.xml

@@ -0,0 +1,264 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="sd-backend-main" status="pending" version="1.0" desc="Backend System Design workflow">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="feature_id" required="false" type="string" desc="Feature identifier, e.g., F-CRM-01"/>
+    <field name="feature_name" required="true" type="string" desc="Feature name, e.g., customer-list"/>
+    <field name="platform_id" required="true" type="string" desc="Target platform, e.g., backend-spring, backend-nestjs"/>
+    <field name="iteration_path" required="true" type="string" desc="Absolute path to iteration directory"/>
+    <field name="workspace_path" required="true" type="string" desc="Absolute path to speccrew-workspace"/>
+    <field name="task_id" required="false" type="string" desc="Task ID from dispatch context"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="forbidden" desc="Document creation constraints">
+    <field name="text">NEVER use create_file to write design documents or INDEX directly</field>
+    <field name="text">MUST create by copying template then filling with search_replace</field>
+  </block>
+
+  <block type="rule" id="R2" level="forbidden" desc="Full-file rewrite prohibition">
+    <field name="text">NEVER replace entire document content in single operation</field>
+    <field name="text">ALWAYS use targeted search_replace on specific sections</field>
+  </block>
+
+  <block type="rule" id="R3" level="mandatory" desc="Template-first workflow">
+    <field name="text">Copy template MUST execute before fill sections</field>
+    <field name="text">Skipping copy and writing content directly is FORBIDDEN</field>
+  </block>
+
+  <block type="rule" id="R4" level="mandatory" desc="Actual framework syntax">
+    <field name="text">All pseudo-code MUST use actual framework/library syntax from techs knowledge</field>
+    <field name="text">NOT generic pseudo-code</field>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="Backend System Design" status="pending" desc="Generate backend detailed design documents">
+
+    <!-- Step 1: Read Inputs -->
+    <block type="task" id="B1" action="read-file" desc="Read Feature Spec document">
+      <field name="path">${iteration_path}/02.feature-design/${feature_id}-${feature_name}-feature-spec.md</field>
+      <field name="fallback_path">${iteration_path}/02.feature-design/${feature_name}-feature-spec.md</field>
+      <field name="output" var="feature_spec"/>
+    </block>
+
+    <block type="task" id="B2" action="read-file" desc="Read API Contract">
+      <field name="path">${iteration_path}/02.feature-design/${feature_id}-${feature_name}-api-contract.md</field>
+      <field name="fallback_path">${iteration_path}/02.feature-design/${feature_name}-api-contract.md</field>
+      <field name="output" var="api_contract"/>
+    </block>
+
+    <!-- Read Techs Knowledge -->
+    <block type="task" id="B3" action="read-file" desc="Read tech-stack.md">
+      <field name="path">${workspace_path}/knowledges/techs/${platform_id}/tech-stack.md</field>
+      <field name="output" var="tech_stack"/>
+    </block>
+
+    <block type="task" id="B4" action="read-file" desc="Read architecture.md">
+      <field name="path">${workspace_path}/knowledges/techs/${platform_id}/architecture.md</field>
+      <field name="output" var="architecture"/>
+    </block>
+
+    <block type="task" id="B5" action="read-file" desc="Read conventions-design.md">
+      <field name="path">${workspace_path}/knowledges/techs/${platform_id}/conventions-design.md</field>
+      <field name="output" var="conventions_design"/>
+    </block>
+
+    <block type="task" id="B6" action="read-file" desc="Read conventions-dev.md">
+      <field name="path">${workspace_path}/knowledges/techs/${platform_id}/conventions-dev.md</field>
+      <field name="output" var="conventions_dev"/>
+    </block>
+
+    <block type="task" id="B7" action="read-file" desc="Read conventions-data.md">
+      <field name="path">${workspace_path}/knowledges/techs/${platform_id}/conventions-data.md</field>
+      <field name="output" var="conventions_data"/>
+    </block>
+
+    <!-- Step 2: Analyze Existing Code Structure -->
+    <block type="task" id="B8" action="analyze" desc="Analyze codebase structure">
+      <field name="analysis_targets">
+        - Controller/Router layer structure
+        - Service layer organization
+        - Repository/DAO layer patterns
+        - Entity/Model definitions
+        - Middleware stack
+        - Exception handling patterns
+        - Database migration structure
+        - Naming conventions
+      </field>
+      <field name="output" var="codebase_analysis"/>
+    </block>
+
+    <!-- Step 3: Extract Functions from Feature Spec -->
+    <block type="task" id="B9" action="analyze" desc="Extract backend functions">
+      <field name="input" value="${feature_spec}">${api_contract}</field>
+      <field name="extraction_rules">
+        - Parse Feature Spec Section 2.N pattern
+        - Extract API interfaces from backend part
+        - Extract data access requirements
+        - Extract business logic flow
+        - Extract cross-module dependencies
+        - Mark each function as [EXISTING], [MODIFIED], or [NEW]
+      </field>
+      <field name="output" var="extracted_functions"/>
+    </block>
+
+    <!-- Checkpoint A: Present function list for confirmation -->
+    <block type="event" id="E1" action="confirm" title="Function List Confirmation" type="yesno" desc="Present function extraction summary">
+      <field name="preview">Backend Functions Extracted for: ${feature_name}
+Platform: ${platform_id}
+
+Function List:
+${extracted_functions.summary}
+
+Markers:
+- [NEW]: ${extracted_functions.new_count} modules
+- [MODIFIED]: ${extracted_functions.modified_count} modules
+- [EXISTING]: ${extracted_functions.existing_count} modules (no design needed)
+
+Confirm function list before proceeding?</field>
+    </block>
+
+    <!-- Step 4: Generate Module Design Documents -->
+    <block type="task" id="B10" action="read-file" desc="Read design template">
+      <field name="path">speccrew-sd-backend/templates/SD-BACKEND-TEMPLATE.md</field>
+      <field name="output" var="design_template"/>
+    </block>
+
+    <!-- Loop: Generate design for each function -->
+    <block type="loop" id="L1" over="${extracted_functions.functions}" as="function" desc="Generate module design documents">
+      <block type="task" id="B11" action="generate" desc="Copy template and create document">
+        <field name="template" value="${design_template}"/>
+        <field name="placeholders">
+          - {Module Name} → ${function.module_name}
+          - {Feature Name} → ${feature_name}
+          - {Platform ID} → ${platform_id}
+        </field>
+        <field name="output_path">${iteration_path}/03.system-design/${platform_id}/${function.module_name}-design.md</field>
+        <field name="output" var="module_doc_created"/>
+      </block>
+
+      <block type="task" id="B12" action="edit-file" desc="Fill Module Structure section">
+        <field name="path">${iteration_path}/03.system-design/${platform_id}/${function.module_name}-design.md</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${tech_stack}${conventions_design}</field>
+        <field name="section">Module Structure</field>
+      </block>
+
+      <block type="task" id="B13" action="edit-file" desc="Fill Interface Pseudo-code section">
+        <field name="path">${iteration_path}/03.system-design/${platform_id}/${function.module_name}-design.md</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${api_contract}${conventions_dev}</field>
+        <field name="section">Interface Pseudo-code</field>
+      </block>
+
+      <block type="task" id="B14" action="edit-file" desc="Fill Database Design section">
+        <field name="path">${iteration_path}/03.system-design/${platform_id}/${function.module_name}-design.md</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${feature_spec}${conventions_data}</field>
+        <field name="section">Database Design</field>
+      </block>
+
+      <block type="task" id="B15" action="edit-file" desc="Fill Transaction Boundaries section">
+        <field name="path">${iteration_path}/03.system-design/${platform_id}/${function.module_name}-design.md</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${conventions_data}</field>
+        <field name="section">Transaction Boundaries</field>
+      </block>
+
+      <block type="task" id="B16" action="edit-file" desc="Fill Exception Handling section">
+        <field name="path">${iteration_path}/03.system-design/${platform_id}/${function.module_name}-design.md</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${api_contract}${conventions_dev}</field>
+        <field name="section">Exception Handling</field>
+      </block>
+    </block>
+
+    <!-- Step 5: Generate Platform INDEX.md -->
+    <block type="task" id="B17" action="read-file" desc="Read index template">
+      <field name="path">speccrew-sd-backend/templates/INDEX-TEMPLATE.md</field>
+      <field name="output" var="index_template"/>
+    </block>
+
+    <block type="task" id="B18" action="generate" desc="Create INDEX.md from template">
+      <field name="template" value="${index_template}"/>
+      <field name="placeholders">
+        - {Platform Name} → ${platform_id}
+        - {Feature Name} → ${feature_name}
+      </field>
+      <field name="output_path">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+    </block>
+
+    <block type="task" id="B19" action="edit-file" desc="Fill Tech Stack Summary">
+      <field name="path">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+      <field name="operation">search_replace</field>
+      <field name="content_source">${tech_stack}</field>
+      <field name="section">Tech Stack Summary</field>
+    </block>
+
+    <block type="task" id="B20" action="edit-file" desc="Fill Shared Design Decisions">
+      <field name="path">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+      <field name="operation">search_replace</field>
+      <field name="content_source">${architecture}${conventions_design}</field>
+      <field name="section">Shared Design Decisions</field>
+    </block>
+
+    <block type="task" id="B21" action="edit-file" desc="Fill Module List Table">
+      <field name="path">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+      <field name="operation">search_replace</field>
+      <field name="content_source">${extracted_functions}</field>
+      <field name="section">Module List Table</field>
+    </block>
+
+    <block type="task" id="B22" action="edit-file" desc="Fill Database Schema Overview">
+      <field name="path">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+      <field name="operation">search_replace</field>
+      <field name="content_source">${extracted_functions}</field>
+      <field name="section">Database Schema Overview</field>
+    </block>
+
+    <!-- Step 6: Present Summary -->
+    <block type="event" id="E2" action="log" level="info" desc="Present design summary">
+      <field name="message">Backend System Design Summary for: ${feature_name}
+Platform: ${platform_id}
+
+Module Designs: ${extracted_functions.design_count}
+├── [NEW] ${extracted_functions.new_count} modules
+├── [MODIFIED] ${extracted_functions.modified_count} modules
+└── [EXISTING] ${extracted_functions.existing_count} modules (no design needed)
+
+Database Changes:
+├── New Tables: ${extracted_functions.new_tables_count}
+├── Modified Tables: ${extracted_functions.modified_tables_count}
+└── Migration Files: ${extracted_functions.migration_count}
+
+Files Generated:
+- ${iteration_path}/03.system-design/${platform_id}/INDEX.md
+${extracted_functions.file_list}</field>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="status" value="SUCCESS" type="string" desc="Task completion status"/>
+    <field name="task_id" from="${task_id}" type="string" desc="Task ID"/>
+    <field name="platform" value="${platform_id}" type="string" desc="Target platform"/>
+    <field name="feature_id" from="${feature_id}" type="string" desc="Feature ID"/>
+    <field name="feature" value="${feature_name}" type="string" desc="Feature name"/>
+    <field name="output_files" type="array" desc="List of generated files">
+      <field name="file">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+      <field name="files" from="${extracted_functions.output_files}"/>
+    </field>
+    <field name="summary" value="Backend system design completed for ${feature_name} on ${platform_id}" type="string" desc="Completion summary"/>
+  </block>
+
+</workflow>