speccrew 0.7.62 → 0.7.64

package/.speccrew/skills/speccrew-sd-desktop/SKILL.xml

@@ -0,0 +1,545 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="sd-desktop-main" status="pending" version="1.0" desc="Desktop 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. If provided, use new naming format"/>
+    <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., desktop-electron, desktop-tauri"/>
+    <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 identifier in DISPATCH-PROGRESS.json. Used for status tracking"/>
+    <field name="skip_confirmation" required="false" type="boolean" default="false" desc="When true, skip Checkpoint A user confirmation (used in batch dispatch mode)"/>
+    <field name="skip_index_generation" required="false" type="boolean" default="false" desc="When true, skip Step 5 INDEX.md generation (INDEX.md will be generated by orchestrator after all workers complete)"/>
+    <field name="index_only" required="false" type="boolean" default="false" desc="When true, skip Steps 1-4 and ONLY execute Step 5 (INDEX.md generation). Used after all platform workers complete"/>
+    <field name="dispatch_progress_file" required="false" type="string" desc="Path to DISPATCH-PROGRESS.json. If provided, worker updates its own task status on completion"/>
+    <field name="update_progress_script" required="false" type="string" desc="Path to update-progress.js script"/>
+  </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">Documents MUST be created by copying template then filling with search_replace</field>
+    <field name="text">create_file produces truncated output on large files</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>
+    <field name="text">Include actual import statements</field>
+    <field name="text">Use actual store/API patterns from conventions</field>
+  </block>
+
+  <block type="rule" id="R5" level="forbidden" desc="TODO/FIXME placeholders">
+    <field name="text">Design documents MUST contain complete implementation logic</field>
+    <field name="text">Do NOT use TODO, FIXME, HACK, or any placeholder comments</field>
+    <field name="text">Every component, method, and interaction MUST be fully specified with actual pseudocode</field>
+  </block>
+
+  <block type="rule" id="R6" level="mandatory" desc="Output filename pattern">
+    <field name="text">Output filename MUST follow pattern: {feature_id}-{feature_name}-design.md</field>
+    <field name="text">Omitting feature_id or using alternative naming is FORBIDDEN</field>
+  </block>
+
+  <block type="rule" id="R7" level="mandatory" desc="Mermaid for all diagrams">
+    <field name="text">ALL component trees, interaction flows, and state management diagrams MUST use Mermaid syntax</field>
+    <field name="text">Use graph TB, sequenceDiagram, flowchart</field>
+    <field name="text">Plain text ASCII diagrams are FORBIDDEN for these sections</field>
+  </block>
+
+  <block type="rule" id="R8" level="mandatory" desc="API route consistency">
+    <field name="text">All API routes in design document MUST exactly match routes defined in API Contract</field>
+    <field name="text">Before writing any route, READ the API Contract and copy routes verbatim</field>
+    <field name="text">Do NOT invent or modify routes</field>
+  </block>
+
+  <block type="rule" id="R9" level="mandatory" desc="Cross-feature dependency marking">
+    <field name="text">When referencing functionality from another Feature, MUST explicitly mark as [DEPENDENCY: F-XXX-NNN]</field>
+    <field name="text">Define a degradation strategy (e.g., hide button, show placeholder) for when that Feature is not yet implemented</field>
+  </block>
+
+  <block type="rule" id="R10" level="mandatory" desc="Status markers required">
+    <field name="text">Use [EXISTING], [MODIFIED], [NEW] markers for all components and store modules</field>
+  </block>
+
+  <block type="rule" id="R11" level="mandatory" desc="Follow techs conventions">
+    <field name="text">Naming, directory structure, patterns must follow techs knowledge</field>
+    <field name="text">Component naming follows conventions-dev.md</field>
+    <field name="text">Directory structure follows conventions-design.md</field>
+  </block>
+
+  <block type="rule" id="R12" level="mandatory" desc="Direct-to-File Output">
+    <field name="text">All design content MUST be written directly to output files</field>
+  </block>
+
+  <block type="rule" id="R13" level="mandatory" desc="Minimal Conversation Output">
+    <field name="text">Only output block execution announcements, error messages, and Task Completion Report</field>
+  </block>
+
+  <block type="rule" id="R14" level="forbidden" desc="No conversation document output">
+    <field name="text">NEVER display full document sections, Mermaid diagrams, API endpoint listings, data model tables in conversation</field>
+    <field name="text">NEVER display architecture descriptions longer than 2 lines in conversation</field>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="Desktop System Design" status="pending" desc="Generate desktop detailed design documents">
+
+    <!-- Gateway: index_only conditional -->
+    <block type="gateway" id="G0" mode="exclusive" desc="Check if index_only mode">
+      <branch test="${index_only} == true" name="Index only - skip to Step 5">
+        <block type="event" id="E0" action="log" level="info" desc="index_only mode active">
+          <field name="message">index_only=true, skipping Steps 1-4 and jumping directly to Step 5 (INDEX.md generation)</field>
+        </block>
+      </branch>
+      <branch default="true" name="Full workflow">
+
+    <!-- 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}/03.api-contract/${feature_id}-${feature_name}-api-contract.md</field>
+      <field name="fallback_path">${iteration_path}/03.api-contract/${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>
+
+    <!-- Optional: Read UI style guide -->
+    <block type="task" id="B7" action="read-file" desc="Read UI style guide">
+      <field name="path">${workspace_path}/knowledges/techs/${platform_id}/ui-style/ui-style-guide.md</field>
+      <field name="optional" value="true"/>
+      <field name="output" var="ui_style_guide"/>
+    </block>
+
+    <!-- Step 2: Analyze Existing Code Structure -->
+    <block type="task" id="B8" action="analyze" desc="Analyze desktop codebase structure">
+      <field name="analysis_targets">
+        - Main process: src/main/**/*.{ts,js} or src-tauri/src/**/*.rs
+        - Renderer process: src/renderer/**/*.{tsx,vue,html}
+        - IPC definitions: src/main/ipc/**/* or src-tauri/src/commands/**/*.rs
+        - Window management patterns
+        - Preload scripts: src/preload/**/* or preload.{ts,js}
+        - Native modules: src/main/native/**/*
+        - State management: src/renderer/stores/**/* or src/stores/**/*
+        - API layer: src/renderer/apis/**/* or src/apis/**/*
+      </field>
+      <field name="output" var="codebase_analysis"/>
+    </block>
+
+    <!-- Step 3: Extract Functions from Feature Spec -->
+    <block type="task" id="B9" action="analyze" desc="Extract desktop functions from Feature Spec">
+      <field name="input" value="${feature_spec}">${api_contract}</field>
+      <field name="extraction_rules">
+        - Parse Feature Spec Section 2.N pattern
+        - Each Feature Spec typically contains 3-8 functions (fine-grained format)
+        - Extract UI prototype for each function
+        - Extract interaction flow (user actions and system responses)
+        - Extract backend API calls from API Contract
+        - Extract local operations (file system, native API, local DB)
+        - Extract data requirements (fields and structures needed)
+        - Mark components as [EXISTING], [MODIFIED], or [NEW]
+      </field>
+      <field name="output" var="extracted_functions"/>
+    </block>
+
+    <!-- Checkpoint A: Function Extraction Confirmation -->
+    <block type="gateway" id="G1" mode="exclusive" desc="Handle Checkpoint A - skip_confirmation gateway">
+      <branch test="${skip_confirmation} == true" name="Skip confirmation - auto proceed">
+        <block type="event" id="E1_skip" action="log" level="info" desc="Skipping Checkpoint A">
+          <field name="message">skip_confirmation=true, logging function extraction summary and proceeding automatically</field>
+        </block>
+      </branch>
+      <branch default="true" name="Request user confirmation">
+        <block type="event" id="E1" action="confirm" title="Function Extraction Confirmation - Checkpoint A" type="yesno" desc="Present function extraction summary">
+          <field name="preview">Desktop Functions Extracted for: ${feature_name}
+Platform: ${platform_id}
+
+Function Extraction Summary:
+${extracted_functions.summary}
+
+Component Markers:
+- [NEW]: ${extracted_functions.new_count} components
+- [MODIFIED]: ${extracted_functions.modified_count} components
+- [EXISTING]: ${extracted_functions.existing_count} components
+
+Confirm function extraction before proceeding?</field>
+        </block>
+      </branch>
+    </block>
+
+    <!-- Step 4: Generate Module Design Documents -->
+    <block type="task" id="B10" action="read-file" desc="Read design template">
+      <field name="path">speccrew-sd-desktop/templates/SD-DESKTOP-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">
+      <!-- Gateway: Determine output path based on feature_id -->
+      <block type="gateway" id="G2" mode="exclusive" desc="Determine output path">
+        <branch test="${feature_id} != null" name="With feature_id">
+          <block type="task" id="B11" action="generate" desc="Copy template and create document with feature_id">
+            <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}/${feature_id}-${feature_name}-design.md</field>
+            <field name="output" var="module_doc_created"/>
+          </block>
+        </branch>
+        <branch default="true" name="Without feature_id (backward compatibility)">
+          <block type="task" id="B12" action="generate" desc="Copy template and create document without feature_id">
+            <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>
+        </branch>
+      </block>
+
+      <!-- Fill each section using search_replace -->
+      <block type="task" id="B13" action="edit-file" desc="Fill Process Architecture section">
+        <field name="path">${module_doc_created.path}</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${architecture}${tech_stack}</field>
+        <field name="section">Process Architecture</field>
+        <field name="rules">
+          - Use actual framework patterns (Electron main/renderer or Tauri command/event)
+          - ALL process architecture diagrams MUST use Mermaid syntax
+          - Mark each process/thread as [EXISTING], [MODIFIED], or [NEW]
+        </field>
+      </block>
+
+      <block type="task" id="B14" action="edit-file" desc="Fill IPC Channels section">
+        <field name="path">${module_doc_created.path}</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${conventions_design}${function}</field>
+        <field name="section">IPC Channels</field>
+        <field name="rules">
+          - Define channel names, request/response types, and serialization format
+          - IPC flow diagrams MUST use Mermaid syntax
+        </field>
+      </block>
+
+      <block type="task" id="B15" action="edit-file" desc="Fill Window Design section">
+        <field name="path">${module_doc_created.path}</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${feature_spec}${conventions_design}</field>
+        <field name="section">Window Design</field>
+        <field name="rules">
+          - Window dimensions, lifecycle, state management
+          - Modal/dialog behavior
+          - Multi-window coordination if applicable
+        </field>
+      </block>
+
+      <block type="task" id="B16" action="edit-file" desc="Fill Native Integration section">
+        <field name="path">${module_doc_created.path}</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${function}${tech_stack}</field>
+        <field name="section">Native Integration</field>
+        <field name="rules">
+          - Actual native API or module usage patterns
+          - Platform-specific considerations (Windows/macOS/Linux)
+        </field>
+      </block>
+
+      <block type="task" id="B17" action="edit-file" desc="Fill Local Storage section">
+        <field name="path">${module_doc_created.path}</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${conventions_design}</field>
+        <field name="section">Local Storage</field>
+        <field name="rules">
+          - Local DB, file system, or electron-store patterns
+          - Data schema and persistence strategy
+        </field>
+      </block>
+
+      <block type="task" id="B18" action="edit-file" desc="Fill Security section">
+        <field name="path">${module_doc_created.path}</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${architecture}${conventions_design}</field>
+        <field name="section">Security</field>
+        <field name="rules">
+          - Context isolation, CSP, preload script security
+          - Permission model and secure IPC practices
+        </field>
+      </block>
+
+      <block type="task" id="B19" action="edit-file" desc="Fill Auto-update section">
+        <field name="path">${module_doc_created.path}</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${tech_stack}</field>
+        <field name="section">Auto-update</field>
+        <field name="rules">
+          - Update check strategy, download flow, restart behavior
+          - Use actual updater library patterns from techs knowledge
+        </field>
+      </block>
+
+      <block type="task" id="B20" action="edit-file" desc="Fill Pseudo-code section">
+        <field name="path">${module_doc_created.path}</field>
+        <field name="operation">search_replace</field>
+        <field name="content_source">${conventions_dev}${function}</field>
+        <field name="section">Pseudo-code</field>
+        <field name="rules">
+          - MUST use actual framework API syntax from techs knowledge
+          - NOT generic pseudo-code
+          - Include actual import statements
+          - Use actual store/API patterns from conventions
+        </field>
+      </block>
+
+      <!-- Step 4.3: Verify Output -->
+      <block type="task" id="B21" action="verify" desc="Verify completed design document">
+        <field name="verification_rules">
+          - All sections filled with actual content (no remaining placeholders)
+          - Mermaid diagrams render correctly
+          - Pseudo-code uses actual framework syntax from techs knowledge
+          - If a section has no applicable content, section title kept with "N/A"
+          - All section titles and numbering preserved
+        </field>
+        <field name="output" var="design_doc_verified"/>
+      </block>
+    </block>
+
+      </branch>
+    </block>
+
+    <!-- Gateway: skip_index_generation conditional -->
+    <block type="gateway" id="G3" mode="exclusive" desc="Check if skip_index_generation">
+      <branch test="${skip_index_generation} == true" name="Skip INDEX.md generation">
+        <block type="event" id="E2_skip" action="log" level="info" desc="Skipping INDEX.md generation">
+          <field name="message">skip_index_generation=true, skipping Step 5 (INDEX.md will be generated by orchestrator after all workers complete)</field>
+        </block>
+      </branch>
+      <branch default="true" name="Generate INDEX.md">
+
+    <!-- Step 5: Generate Platform INDEX.md -->
+    <block type="task" id="B22" action="read-file" desc="Read index template">
+      <field name="path">speccrew-sd-desktop/templates/INDEX-TEMPLATE.md</field>
+      <field name="output" var="index_template"/>
+    </block>
+
+    <block type="task" id="B23" 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>
+      <field name="output" var="index_doc_created"/>
+    </block>
+
+    <block type="task" id="B24" 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="B25" action="edit-file" desc="Fill Target Operating Systems">
+      <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">Target Operating Systems</field>
+    </block>
+
+    <block type="task" id="B26" action="edit-file" desc="Fill Process Architecture Strategy">
+      <field name="path">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+      <field name="operation">search_replace</field>
+      <field name="content_source">${architecture}</field>
+      <field name="section">Process Architecture Strategy</field>
+    </block>
+
+    <block type="task" id="B27" action="edit-file" desc="Fill IPC Patterns">
+      <field name="path">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+      <field name="operation">search_replace</field>
+      <field name="content_source">${conventions_design}</field>
+      <field name="section">IPC Patterns</field>
+    </block>
+
+    <block type="task" id="B28" action="edit-file" desc="Fill Security Model">
+      <field name="path">${iteration_path}/03.system-design/${platform_id}/INDEX.md</field>
+      <field name="operation">search_replace</field>
+      <field name="content_source">${architecture}</field>
+      <field name="section">Security Model</field>
+    </block>
+
+    <block type="task" id="B29" action="edit-file" desc="Fill Module List">
+      <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</field>
+      <field name="module_list_rules">
+        - Column ID: Use feature_id if available (e.g., F-CRM-01), otherwise use module name
+        - Column Name: Feature or module name
+        - Column Document: Link to design file (e.g., F-CRM-01-customer-list-design.md)
+        - Column Status: [NEW], [MODIFIED], or [EXISTING]
+        - Example row: | F-CRM-01 | Customer List | F-CRM-01-customer-list-design.md | NEW |
+      </field>
+    </block>
+
+    <!-- Step 5.4: Verify INDEX.md Output -->
+    <block type="task" id="B30" action="verify" desc="Verify completed INDEX.md">
+      <field name="verification_rules">
+        - All sections filled with actual content (no remaining placeholders)
+        - All module design documents are correctly linked
+        - Platform-level summary is complete
+      </field>
+      <field name="output" var="index_doc_verified"/>
+    </block>
+
+      </branch>
+    </block>
+
+    <!-- Step 6: Present Summary -->
+    <block type="event" id="E3" action="log" level="info" desc="Present design summary">
+      <field name="message">Desktop System Design Summary for: ${feature_name}
+Platform: ${platform_id}
+Framework: ${tech_stack.framework}
+
+Module Design Documents: ${extracted_functions.design_count}
+${extracted_functions.file_list}
+
+Key Design Decisions:
+- Process Architecture: ${architecture.process_model}
+- IPC Strategy: ${conventions_design.ipc_pattern}
+- State Management: ${conventions_design.state_management}
+- Security Model: ${architecture.security_model}
+- Auto-Update: ${tech_stack.updater}
+
+Concerns/Trade-offs:
+- ${concerns_list}
+
+Please confirm:
+1. Are the process architectures appropriate?
+2. Is the IPC communication design correct?
+3. Do the pseudo-code patterns match project conventions?
+4. Are all API calls from API Contract covered?
+5. Is the native integration approach suitable?</field>
+    </block>
+
+    <!-- Step 7: Update Task Status (conditional) -->
+    <block type="gateway" id="G4" mode="exclusive" desc="Check if dispatch_progress_file provided">
+      <branch test="${dispatch_progress_file} != null AND ${task_id} != null" name="Update task status">
+        <block type="gateway" id="G4a" mode="exclusive" desc="Determine success or failure">
+          <branch test="${workflow_status} == 'SUCCESS'" name="Mark completed">
+            <block type="task" id="B31" action="run-script" desc="Update task status to completed">
+              <field name="command">node "${update_progress_script}" update-task --file "${dispatch_progress_file}" --task-id "${task_id}" --status completed</field>
+              <field name="output" var="status_update_result"/>
+            </block>
+          </branch>
+          <branch default="true" name="Mark failed">
+            <block type="task" id="B32" action="run-script" desc="Update task status to failed">
+              <field name="command">node "${update_progress_script}" update-task --file "${dispatch_progress_file}" --task-id "${task_id}" --status failed</field>
+              <field name="output" var="status_update_result"/>
+            </block>
+          </branch>
+        </block>
+      </branch>
+      <branch default="true" name="No status update needed">
+        <block type="event" id="E4" action="log" level="info" desc="No dispatch_progress_file provided">
+          <field name="message">dispatch_progress_file or task_id not provided, skipping status update</field>
+        </block>
+      </branch>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results - SUCCESS scenario">
+    <field name="status" value="SUCCESS" type="string" desc="Task completion status"/>
+    <field name="task_id" from="${task_id}" type="string" desc="Task ID from context"/>
+    <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="Desktop system design completed for ${feature_name} on ${platform_id} with ${extracted_functions.design_count} module designs" type="string" desc="Completion summary"/>
+  </block>
+
+  <block type="output" id="O2" desc="Workflow output results - FAILED scenario">
+    <field name="status" value="FAILED" type="string" desc="Task completion status"/>
+    <field name="task_id" from="${task_id}" type="string" desc="Task ID from context"/>
+    <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" value="[]" type="array" desc="No output files generated"/>
+    <field name="error" type="string" desc="Description of what went wrong"/>
+    <field name="error_category" type="string" desc="DEPENDENCY_MISSING | VALIDATION_ERROR | BLOCKED"/>
+    <field name="recovery_hint" type="string" desc="Suggestion for how to resolve or retry"/>
+  </block>
+
+  <!-- ============================================================
+       Quality Verification Checklist
+       ============================================================ -->
+  <block type="checklist" id="CK1" desc="Quality verification checklist">
+    <field name="item">All techs knowledge documents loaded before design</field>
+    <field name="item">Existing code structure analyzed via Glob/Grep</field>
+    <field name="item">Every Feature Spec function covered in a module design</field>
+    <field name="item">All API calls from API Contract referenced correctly</field>
+    <field name="item">Pseudo-code uses actual framework syntax (not generic)</field>
+    <field name="item">Component naming follows conventions-dev.md</field>
+    <field name="item">State management follows architecture.md patterns</field>
+    <field name="item">Directory structure follows conventions-design.md</field>
+    <field name="item">INDEX.md generated with complete module list</field>
+    <field name="item">All files written to correct paths under 03.system-design/{platform_id}/</field>
+    <field name="item">Output file named as {feature_id}-{feature_name}-design.md</field>
+    <field name="item">Checkpoint A passed (or skipped via skip_confirmation)</field>
+    <field name="item">No TODO/FIXME placeholders - all components have complete pseudocode</field>
+    <field name="item">API routes match API Contract exactly</field>
+    <field name="item">Cross-Feature dependencies explicitly marked</field>
+    <field name="item">Mermaid diagrams used - no ASCII text diagrams</field>
+  </block>
+
+</workflow>