speccrew 0.7.62 → 0.7.64

package/.speccrew/skills/speccrew-knowledge-techs-generate/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-knowledge-techs-generate
 description: Stage 2 of technology knowledge initialization - Generate technology documentation for a specific platform using XML workflow blocks. Extracts tech stack, architecture, and conventions from configuration files and source code. Creates INDEX.md, tech-stack.md, architecture.md, and conventions-*.md files. Used by Worker Agent in parallel for each detected platform.
 tools: Read, Write, Glob, Grep, Skill
@@ -38,7 +38,7 @@ Generate comprehensive technology documentation for a specific platform by analy
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-knowledge-techs-generate-conventions/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-knowledge-techs-generate-conventions
 description: Generate technology convention documents (INDEX, tech-stack, architecture, conventions-*) for a specific platform using XML Block workflow. Extracts tech stack, architecture, and development conventions from configuration files and source code. Split from techs-generate for parallel execution with ui-style worker.
 tools: Read, Write, Glob, Grep
@@ -72,7 +72,7 @@ ${output_path}/
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-knowledge-techs-generate-quality/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-knowledge-techs-generate-quality
 description: Quality assurance for generated tech documentation using XML workflow blocks. Performs cross-validation, consistency checks, completeness verification, and generates quality reports.
 tools: Read, Write, Glob, Grep, Bash
@@ -33,7 +33,7 @@ Worker Agent (speccrew-task-worker)
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-knowledge-techs-generate-ui-style/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-knowledge-techs-generate-ui-style
 description: Generate UI style analysis documents for a specific frontend platform using XML workflow blocks. Analyzes page types, components, layouts, and styling conventions from source code. Only applicable to frontend platforms (web, mobile, desktop).
 tools: Read, Write, Glob, Grep, Skill
@@ -40,7 +40,7 @@ Worker Agent (speccrew-task-worker)
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-knowledge-techs-index/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-knowledge-techs-index
 description: Stage 3 of technology knowledge initialization - Generate root INDEX.md by aggregating all platform technology documents using XML workflow blocks. Creates the master index that maps platforms to their documentation and provides Agent-to-Platform mapping guide. Used by Worker Agent after all platform documents are generated.
 tools: Read, Write, Skill
@@ -48,7 +48,7 @@ Worker Agent (speccrew-task-worker)
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-knowledge-techs-init/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-knowledge-techs-init
 description: Stage 1 of technology knowledge initialization - Scan source code to detect technology platforms and generate techs-manifest.json using XML workflow blocks. Identifies web, mobile, backend, and desktop platforms by analyzing configuration files and project structure. Used by Worker Agent to kick off the techs pipeline.
 tools: Read, Write, Glob, Grep, SearchCodebase, Skill
@@ -41,7 +41,7 @@ Worker Agent (speccrew-task-worker)
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-knowledge-techs-ui-analyze/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-knowledge-techs-ui-analyze
 description: Analyze existing frontend UI codebase to extract and summarize page styles, layout patterns, component usage, and design conventions. Generates comprehensive UI style guides for each platform (PC, Mobile, etc.) including page type classifications, component libraries, layout patterns, and styling conventions. Used to ensure new pages maintain consistency with existing system design.
 tools: Read, Write, Glob, Grep
@@ -74,7 +74,7 @@ Generate the following documents in `{output_path}/`:
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-knowledge-detector/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-knowledge-detector
 description: Detect business knowledge base availability and completeness status. Scans sync-state directory to determine if full knowledge (system-overview.md), lite knowledge (features-*.json), or no knowledge is available.
 tools: Read, Glob
@@ -60,7 +60,7 @@ Detect business knowledge base availability and completeness status. Scans the s
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-module-initializer/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-module-initializer
 description: Generate analyze task plan for a single business module. Reads features-*.json, filters matched module's pending features, and outputs a task plan JSON (list of features to analyze with analyzer parameters). Used by Worker Agent, invoked by PM Agent for on-demand module task planning.
 tools: Read, Write, Skill, Bash
@@ -99,7 +99,7 @@ Example: `"ki-web-vue-system-index"`
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-module-matcher/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-module-matcher
 description: Match user requirement text against business knowledge base features to identify related modules. Reads features-*.json and performs semantic matching.
 tools: Read
@@ -67,7 +67,7 @@ Match user requirement text against business knowledge base features to identify
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-phase0-init/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-phase0-init
 description: SpecCrew PM Phase 0 Initialization Skill. Handles iteration directory creation, WORKFLOW-PROGRESS.json management, checkpoint recovery, IDE detection, and path initialization. First step before any PM workflow execution.
 tools: Read, Write, Glob, Grep
@@ -49,7 +49,7 @@ Applies workspace initialization principles:
 
 # AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-phase1-knowledge-check/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-phase1-knowledge-check
 description: SpecCrew PM Phase 1 Knowledge Base Availability Check Skill. Detects knowledge base status and initializes business knowledge as needed. Supports three-path routing (Full/Lite/None) with Path B deep initialization sequence.
 tools: Read, Write, Glob, Grep, Bash
@@ -48,7 +48,7 @@ Applies knowledge detection and initialization flow:
 
 # AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-phase2-complexity-assess/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-phase2-complexity-assess
 description: Complexity assessment and skill routing for PM Phase 2. Validates knowledge initialization completeness, evaluates requirement complexity across 5 dimensions, and routes to appropriate PRD workflow (simple vs full pipeline). Use after Phase 1 knowledge detection completes.
 tools: Read, Grep
@@ -40,7 +40,7 @@ PM Agent (speccrew-product-manager)
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-phase5-subprd-dispatch/SKILL.md

@@ -1,11 +1,11 @@
-# speccrew-pm-phase5-subprd-dispatch
+# speccrew-pm-phase5-subprd-dispatch
 
 ## Description
 
 PM Phase 5 Sub-PRD Batch Dispatch Skill. **Orchestration-layer skill** executed directly by PM Agent (NOT dispatched to Worker).
 
 This is an **orchestration skill** that PM Agent must execute directly:
-- PM Agent reads `workflow.agentflow.xml` and executes each block step-by-step
+- PM Agent reads `SKILL.xml` and executes each block step-by-step
 - PM Agent uses Agent tool to dispatch Workers for Sub-PRD generation
 - Workers generate Sub-PRD files; PM Agent only coordinates
 
@@ -15,12 +15,12 @@ This is an **orchestration skill** that PM Agent must execute directly:
 - Therefore, this skill MUST be executed by PM Agent directly
 - PM Agent MUST NOT dispatch this skill to a Worker
 
-**Execution Method**: PM Agent reads `workflow.agentflow.xml` and follows the workflow steps.
+**Execution Method**: PM Agent reads `SKILL.xml` and follows the workflow steps.
 
-## MANDATORY: PM Must Read workflow.agentflow.xml
+## MANDATORY: PM Must Read SKILL.xml
 
 > 🛑 **BEFORE executing this skill, PM Agent MUST:**
-> 1. Read the `workflow.agentflow.xml` file in this skill directory
+> 1. Read the `SKILL.xml` file in this skill directory
 > 2. Parse each block and execute in order
 > 3. Follow the exact workflow steps defined in the XML
 >
@@ -51,7 +51,7 @@ This is an **orchestration skill** that PM Agent must execute directly:
 | `sub_prd_files` | array | List of generated Sub-PRD file paths |
 | `feature_list_path` | string | Feature List file path |
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 ## Checklist
 
@@ -88,7 +88,7 @@ This is an **orchestration skill** that PM Agent must execute directly:
 
 ## Must Do
 
-- **READ workflow.agentflow.xml FIRST** — PM Agent must parse the XML workflow before any execution
+- **READ SKILL.xml FIRST** — PM Agent must parse the XML workflow before any execution
 - **Initialize DISPATCH-PROGRESS.json BEFORE any Worker dispatch** — Use update-progress.js init command
 - **Dispatch one Worker per module** — Use Agent tool to create speccrew-task-worker with speccrew-pm-sub-prd-generate skill
 - **Update progress after each Worker completes** — Use update-progress.js update-task command
@@ -98,7 +98,7 @@ This is an **orchestration skill** that PM Agent must execute directly:
 ## Must Not Do
 
 - **DO NOT dispatch this skill to a Worker** — Phase 5 is PM direct execution
-- **DO NOT skip reading workflow.agentflow.xml** — XML workflow is the execution guide
+- **DO NOT skip reading SKILL.xml** — XML workflow is the execution guide
 - **DO NOT dispatch Workers before DISPATCH-PROGRESS.json is initialized** — Progress tracking is mandatory
 - **DO NOT create DISPATCH-PROGRESS.json manually** — Must use update-progress.js script
 - **DO NOT generate Sub-PRD content directly** — Only Workers generate Sub-PRDs

package/.speccrew/skills/speccrew-pm-phase6-verify-confirm/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-phase6-verify-confirm
 description: SpecCrew PM Phase 6 Verification & Confirmation Skill. Performs file integrity validation, feature list completeness check, user review gate, and finalization. Mandatory user confirmation required before status updates.
 tools: Read, Write, Glob, Grep
@@ -48,7 +48,7 @@ Applies three-stage gated verification:
 
 # AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-requirement-analysis/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-requirement-analysis
 description: SpecCrew PM PRD Generation Skill. Generates PRD documents from clarified requirements and module design. Produces Master PRD and Sub-PRD Dispatch Plan for downstream Feature Design. Third step in PRD workflow.
 tools: Read, Write, Glob, Grep
@@ -38,7 +38,7 @@ Applies ISA-95 Stages 2-3 outputs for PRD generation:
 
 # AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-requirement-assess/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-requirement-assess
 description: Quick impact assessment for new requirements. Analyzes affected modules, change type, risk level, and cross-module dependencies using system documentation and knowledge graph. Use when PM Agent needs a lightweight evaluation before deciding whether to run full requirement-analysis workflow.
 tools: Read, Glob, Grep
@@ -38,7 +38,7 @@ PM Agent (speccrew-product-manager)
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-requirement-clarify/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-requirement-clarify
 description: SpecCrew PM Requirement Clarification Skill. Dual-mode support (simple/complex). Produces .clarification-summary.md as interface contract for downstream PRD generation. First step in PRD workflow.
 tools: Read, Write, Glob, Grep
@@ -71,7 +71,7 @@ Step 6: Guard Gateway G3 (sufficiency_checks_passed == true required)
 
 # AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-requirement-model/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-requirement-model
 description: SpecCrew PM Requirement Modeling Skill. Applies ISA-95 Stages 1-3 for business domain analysis, WBS decomposition, and module ordering. Produces .module-design.md as interface contract for downstream PRD generation. Second step in PRD workflow.
 tools: Read, Write, Glob, Grep
@@ -39,7 +39,7 @@ Applies ISA-95 Stages 1-3 as structured analysis framework:
 
 # AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-pm-requirement-simple/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-requirement-simple
 description: SpecCrew PM Simple Requirement Skill. Handles lightweight requirements (field additions, minor feature changes, single-module enhancements) with a streamlined PRD generation process. Produces a single concise PRD document without Master-Sub structure or worker dispatch.
 tools: Read, Write, Glob, Grep, Terminal
@@ -54,7 +54,7 @@ This skill applies ISA-95 Stages 1-3 in lightweight mode:
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

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

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-pm-sub-prd-generate
 description: Generate a single Sub-PRD document for one module. Used by PM Agent's worker dispatch to parallelize Sub-PRD generation across multiple modules. Each worker invocation generates one complete Sub-PRD file based on the PRD template.
 tools: Read, Write, Glob, Grep
@@ -53,7 +53,7 @@ tools: Read, Write, Glob, Grep
 
 # AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 

package/.speccrew/skills/speccrew-product-manager-orchestration/SKILL.md

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-product-manager-orchestration
 version: 2.0.0
 description: Product Manager core orchestration skill (pure routing layer v2.0), responsible for workflow resume routing and dispatch-to-worker scheduling for each Phase Skill. All business logic is executed by independent Phase Skills.
@@ -133,7 +133,7 @@ Phase 0 outputs `resume_target` to control resume routing:
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 ---
 

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

@@ -1,4 +1,4 @@
----
+---
 name: speccrew-sd-backend
 description: Backend System Design SOP. Guide System Designer Agent to generate platform-specific backend detailed design documents by filling technology implementation details into the Feature Spec skeleton. Reads techs knowledge to determine actual framework syntax, ORM patterns, and conventions.
 tools: Read, Write, Glob, Grep
@@ -12,6 +12,6 @@ tools: Read, Write, Glob, Grep
 
 ## AgentFlow Definition
 
-<!-- @agentflow: workflow.agentflow.xml -->
+<!-- @agentflow: SKILL.xml -->
 
 > **REQUIRED**: Read and execute the XML workflow above. The XML contains the complete workflow definition including all steps, rules, conditions, and checklist.

package/.speccrew/skills/speccrew-sd-design-overview-generate/SKILL.md

@@ -1,6 +1,5 @@
----
+---
 name: speccrew-sd-design-overview-generate
-version: 1.0.0
 description: Design Overview Generation Skill for System Designer. Reads Feature Registry, techs-manifest platforms, and framework evaluation results to generate a comprehensive DESIGN-OVERVIEW.md with Feature×Platform matrix index. Invoked by System Designer Agent during Phase 4 via worker dispatch.
 tools: Read, Write, Glob, Grep
 ---
@@ -13,228 +12,6 @@ tools: Read, Write, Glob, Grep
 
 ## 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
-
-> **These rules apply to ALL steps. Violation = task failure.**
-
-1. **READ-ONLY on Feature Spec and API Contract** — NEVER modify Feature Spec or API Contract documents. Only read for reference.
-2. **READ-ONLY on techs-manifest.json** — NEVER modify the techs manifest. Only read for platform information.
-3. **READ-ONLY on framework-evaluation.md** — NEVER modify the framework evaluation report. Only read for technology decisions.
-4. **Single Output Only** — Only create DESIGN-OVERVIEW.md at the specified output_path. No other files.
-5. **Direct-to-File Output** — Write all content directly to DESIGN-OVERVIEW.md. DO NOT display document content in conversation.
-
-## Step 1: Read Inputs
-
-**Input Parameters** (from agent context):
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `workspace_path` | string | Yes | speccrew-workspace root directory path |
-| `iteration_path` | string | Yes | Current iteration directory path |
-| `feature_registry_path` | string | Yes | Path to .prd-feature-list.json |
-| `techs_manifest_path` | string | Yes | Path to techs-manifest.json |
-| `framework_evaluation_path` | string | Yes | Path to framework-evaluation.md |
-| `output_path` | string | No | Output file path (default: iteration_path/03.system-design/DESIGN-OVERVIEW.md) |
-
-Read in order:
-
-1. **Read .prd-feature-list.json** — Extract features array:
-   - `feature_id` (e.g., F-CRM-01) or `module_name` for legacy format
-   - `feature_name` or `module_name`
-   - `feature_spec` path
-   - `api_contract` path
-   - `module`
-   - `type`
-
-2. **Read techs-manifest.json** — Extract platforms array:
-   - `platform_id` (e.g., web-react, backend-nodejs)
-   - `friendly_name`
-   - `tech_stack`
-
-3. **Read framework-evaluation.md** — Extract Technology Decisions:
-   - Framework evaluation results
-   - New dependencies introduced (if any)
-   - Version constraints
-
-## Step 2: Build Feature×Platform Matrix
-
-For each feature × platform combination, generate one matrix row:
-
-| Field | Source |
-|-------|--------|
-| `feature_id` | feature.feature_id (or "-" for legacy format) |
-| `feature_name` | feature.feature_name (or feature.module_name for legacy) |
-| `platform` | platform.friendly_name |
-| `platform_id` | platform.platform_id |
-| `skill` | Map platform_id prefix → speccrew-sd-{type} (see below) |
-| `design_directory` | {platform_id}/{feature_id}-{feature_name}-design.md (new) or {platform_id}/{module}-design.md (legacy) |
-| `status` | Always "pending" |
-
-### Platform ID Prefix → Skill Mapping
-
-| Platform ID Prefix | Target Skill |
-|-------------------|--------------|
-| web-* | speccrew-sd-frontend |
-| backend-* | speccrew-sd-backend |
-| mobile-* | speccrew-sd-mobile |
-| desktop-* | speccrew-sd-desktop |
-
-### Legacy Format Compatibility
-
-If a feature does NOT have a Feature ID (no "F-" prefix):
-- Feature ID column displays `-`
-- Use `module_name` as Feature Name
-- Design Directory uses `{platform_id}/{module_name}-design.md` (legacy format)
-
-## Step 3: Generate DESIGN-OVERVIEW.md
-
-Write the design overview document to `output_path`.
-
-### Document Structure
-
-```markdown
-# System Design Overview - {Iteration Name}
-
-## 1. Design Scope
-
-- **Iteration**: {iteration_identifier}
-- **Platforms**: {platform_list}
-- **Features**: {count} features discovered
-
-### 1.1 Feature List
-
-| Feature ID | Feature Name | Feature Spec | API Contract |
-|------------|--------------|--------------|--------------|
-| (from feature registry, one row per feature) |
-
-> **Legacy Format Compatibility**: If file uses legacy format (no Feature ID), Feature ID column shows `-`, using module name as Feature Name
-
-## 2. Technology Decisions
-
-(from framework-evaluation.md - Phase 3 results)
-
-- Framework evaluation results
-- New dependencies introduced (if any)
-- Version constraints
-
-## 3. Platform Design Index
-
-| Feature ID | Feature Name | Platform | Platform ID | Skill | Design Directory | Status |
-|------------|--------------|----------|-------------|-------|------------------|--------|
-| (Feature × Platform matrix from Step 2) |
-
-> **Notes**:
-> - New Format: Design Directory contains `{feature-id}-{feature-name}` (e.g., `F-CRM-01-customer-list-design.md`)
-> - Legacy Format: Design Directory uses `{module}-design.md`
-
-## 4. Feature Summary (Optional - when Feature count > 5)
-
-### 4.1 Feature by Module
-
-| Module | Feature Count | Feature IDs |
-|--------|---------------|-------------|
-| (group features by module) |
-
-### 4.2 Feature Type Distribution
-
-| Type | Count | Features |
-|------|-------|----------|
-| (group features by type) |
-
-## 5. Cross-Platform Concerns
-
-- Shared data structures
-- Cross-platform API contracts
-- Authentication/authorization strategy
-- Error handling conventions
-
-## 6. Design Constraints
-
-- API Contract is READ-ONLY — do not modify
-- All pseudo-code must use actual framework syntax from techs knowledge
-- Each module design document maps 1:1 to a Feature Spec function
-```
-
-## Step 4: Validate Output
-
-After writing DESIGN-OVERVIEW.md, verify:
-
-- [ ] File exists at output_path
-- [ ] Contains "## 1. Design Scope" section
-- [ ] Contains "## 2. Technology Decisions" section
-- [ ] Contains "## 3. Platform Design Index" table
-- [ ] Platform Design Index covers all Feature × Platform combinations
-- [ ] Feature count matches feature registry
-- [ ] Platform count matches techs-manifest
-- [ ] All index entries have status "pending"
-
-## Step 5: Output Task Completion Report
-
-After validation, output:
-
-```
---- TASK COMPLETION REPORT ---
-Task: Design Overview Generation
-Status: SUCCESS
-Output: {output_path}
-Features: {feature_count}
-Platforms: {platform_count}
-Matrix Entries: {feature_count × platform_count}
---- END REPORT ---
-```
-
-If any step fails:
-
-```
---- TASK COMPLETION REPORT ---
-Task: Design Overview Generation
-Status: FAILED
-Error: {specific error description}
-Failed At: Step {N}
---- END REPORT ---
-```
-
-## OUTPUT EFFICIENCY RULES
-
-When executing this skill:
-
-1. **Direct-to-File Output**: All design overview content MUST be written directly to DESIGN-OVERVIEW.md
-2. **Minimal Conversation Output**: Only output:
-   - Block execution announcements (1 line each): `[Block XX] Building matrix...`
-   - Error messages requiring attention
-   - Task Completion Report (final summary)
-3. **FORBIDDEN in conversation**:
-   - Full document sections or drafts
-   - Feature × Platform matrix tables
-   - Feature list tables
-   - Technology decision excerpts longer than 2 lines
-4. **Rationale**: Workers run in batch mode. Displaying design content in conversation wastes context window and provides no value since content goes to file anyway.
-
-# Key Rules
-
-| Rule | Description |
-|------|-------------|
-| **FORBIDDEN: Input Modification** | Do NOT modify feature specs, API contracts, techs-manifest, or framework-evaluation |
-| **FORBIDDEN: Extra Files** | Do NOT create any files other than DESIGN-OVERVIEW.md |
-| **FORBIDDEN: Conversation Output** | Do NOT display DESIGN-OVERVIEW content in conversation — write directly to file |
-| **MANDATORY: Complete Matrix** | Platform Design Index MUST cover ALL Feature × Platform combinations |
-| **MANDATORY: Pending Status** | ALL Platform Design Index entries MUST have status "pending" |
-
-# Checklist
+<!-- @agentflow: SKILL.xml -->
 
-- [ ] .prd-feature-list.json read and features array extracted
-- [ ] techs-manifest.json read and platforms array extracted
-- [ ] framework-evaluation.md read and technology decisions extracted
-- [ ] Feature format detected (new or legacy)
-- [ ] Feature × Platform matrix built with all combinations
-- [ ] Platform ID prefix correctly mapped to target skills
-- [ ] DESIGN-OVERVIEW.md generated with all required sections
-- [ ] Feature Summary section included only when feature count > 5
-- [ ] Output validated against checklist
-- [ ] Task Completion Report output
+> **REQUIRED**: Read and execute the XML workflow above. The XML contains the complete workflow definition including all steps, rules, conditions, and checklist.