speccrew 0.7.74 → 0.7.76

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

@@ -4,339 +4,12 @@ description: Dispatch techs knowledge base generation tasks with 3-stage pipelin
 tools: Read, Write, Task, Bash
 ---
 
-> **⚠️ MANDATORY EXECUTION PROTOCOL — READ BEFORE EXECUTING ANY BLOCK**
->
-> **Step 1**: Load XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md` — this defines all block types and action-to-tool mappings
->
-> **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
->
-> ```
-> 🏷️ Block [ID] (action=[action]) — [desc]
-> 🔧 Tool: [which IDE tool to call]
-> ✅ Result: [output or status]
-> ```
->
-> Action-to-tool mapping:
-> - `action="run-script"` → Execute via **Terminal tool** (pass the `<field name="command">` value EXACTLY)
-> - `action="run-skill"` → Invoke via **Skill tool** (pass the `<field name="skill">` value EXACTLY)
-> - `action="dispatch-to-worker"` → Create **Task** via **Task tool** for `speccrew-task-worker` (Worker loads and executes the skill, NOT you)
-> - `action="confirm"` (event) → Present to user and wait for response
->
-> **Step 3**: Execute ALL stages sequentially without pausing (only stop at explicit `<event action="confirm">` blocks)
->
-> **FORBIDDEN**:
-> - Do NOT skip the block announcement format above — every block must be announced before execution
-> - Do NOT run terminal commands as substitute for Skill tool calls
-> - Do NOT do Worker's job yourself — when `action="dispatch-to-worker"`, create a Task and let Worker handle it
-> - Do NOT skip blocks or improvise your own commands
-> - Do NOT read a skill's SKILL.md file yourself — use the Skill tool which resolves paths automatically
-
-# Techs Knowledge Dispatch (XML Block Version)
-
-Orchestrate **techs knowledge base generation** with a 3-stage pipeline using **XML Block system**: Platform Detection → Tech Doc Generation → Root Index.
-
-## Invocation Method
-
-**CRITICAL**: This skill is an **orchestration playbook** — it MUST be loaded directly by Team Leader via Skill tool (NOT via Worker Agent).
-
-```
-Correct: Leader uses Skill tool to load this playbook directly
-Incorrect: Dispatch this skill to speccrew-task-worker
-```
-
-**Why?** This skill defines the orchestration workflow and prepares task plans for downstream workers. The Team Leader reads this playbook and dispatches individual worker tasks via Task tool → speccrew-task-worker for each stage.
-
-**Correct Invocation Pattern**:
-```xml
-<block type="task" action="run-skill" desc="Leader directly invokes techs-dispatch as orchestration playbook">
-  <field name="skill">speccrew-knowledge-techs-dispatch</field>
-  <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
-</block>
-```
-
-**Worker Dispatch Rule**:
-- Dispatch skills (bizs-dispatch, techs-dispatch): Leader calls directly via Skill tool
-- Downstream worker skills (techs-init, techs-generate-conventions, techs-generate-ui-style, etc.): Leader dispatches via Task tool → speccrew-task-worker
-
-**FORBIDDEN**: Worker Agents MUST NOT execute this dispatch skill. If a Worker Agent loads this skill, it must report error and abort.
-
-## Quick Reference — Execution Flow
-
-```
-Stage 1: Platform Detection
-  └─ Read techs-manifest.json → Identify platforms & tech stacks
-        ↓
-Stage 2: Tech Doc Generation (PARALLEL)
-  └─ Prepare task plans for techs-generate workers per platform
-  └─ After generate workers complete → prepare quality check worker task plans
-  └─ Monitor completion markers
-        ↓
-Stage 2.5: Completion Verification
-  └─ Step A: Scan completion markers
-  └─ Step B: Verify output integrity
-  └─ Step C: Update progress status
-        ↓
-Stage 3: Root Index Generation
-  └─ Generate techs/README.md root index
-  └─ Cross-platform consistency check
-```
-
-> **NOTE**: All worker dispatch operations are handled by the calling Agent (Team Leader). This Skill only prepares task plans and monitors completion markers.
-
-## Language Adaptation
-
-**CRITICAL**: All generated documents must match the user's language. Detect the language from the user's input and pass it to all downstream Worker Agents.
-
-- User writes in 中文 → Generate Chinese documents, pass `language: "zh"` to workers
-- User writes in English → Generate English documents, pass `language: "en"` to workers
-- User writes in other languages → Use appropriate language code
-
-**All downstream skills must receive the `language` parameter and generate content in that language only.**
-
-## Trigger Scenarios
-
+# Trigger Scenarios
 - "Initialize techs knowledge base"
 - "Generate technology knowledge from source code"
 - "Dispatch techs knowledge generation"
 
-## User
-
-Leader Agent (speccrew-team-leader)
-
-## Platform Naming Convention
-
-Read `speccrew-workspace/docs/configs/platform-mapping.json` for standardized platform mapping rules.
-
-| Concept | techs-init (techs-manifest.json) | Example (UniApp) |
-|---------|----------------------------------|------------------|
-| **Category** | `platform_type` | `mobile` |
-| **Technology** | `framework` | `uniapp` |
-| **Identifier** | `platform_id` | `mobile-uniapp` |
-
-## Input
-
-| Variable | Description | Default |
-|----------|-------------|---------|
-| `source_path` | Source code root path | project root |
-| `language` | User's language code (e.g., "zh", "en") | **REQUIRED** |
-
-## Output
-
-- Platform manifest: `speccrew-workspace/knowledges/base/sync-state/knowledge-techs/techs-manifest.json`
-- Tech docs: `speccrew-workspace/knowledges/techs/{platform_id}/`
-- Root index: `speccrew-workspace/knowledges/techs/INDEX.md`
-- Status files: `speccrew-workspace/knowledges/base/sync-state/knowledge-techs/stage{N}-status.json`
-
----
-
 ## AgentFlow Definition
-
 <!-- @agentflow: SKILL.xml -->
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
->
-> After reading the specification, parse the XML workflow below and **strictly execute each `<block>` in document order**. Every `<block type="task">` is a literal tool-call instruction — use the `action` attribute to determine which IDE tool to invoke, and pass the `<field name="command">` or `<field name="skill">` value **exactly as written**. Do NOT interpret the workflow as a goal description or improvise your own approach.
-
-
-
----
-
-## Appendix: Reference
-
-### Worker Completion Marker Format
-
-Each Worker MUST create a completion marker file after generating documents.
-
-#### Conventions Worker Done File
-
-**File**: `{completed_dir}/{platform_id}.done-conventions.json`
-
-**Format**:
-```json
-{
-  "platform_id": "web-vue",
-  "worker_type": "conventions",
-  "status": "completed",
-  "documents_generated": [
-    "INDEX.md", "tech-stack.md", "architecture.md",
-    "conventions-dev.md", "conventions-design.md",
-    "conventions-unit-test.md", "conventions-build.md"
-  ],
-  "analysis_file": "web-vue.analysis-conventions.json",
-  "completed_at": "2024-01-15T10:45:00Z"
-}
-```
-
-#### UI-Style Worker Done File
-
-**File**: `{completed_dir}/{platform_id}.done-ui-style.json`
-
-**Format**:
-```json
-{
-  "platform_id": "web-vue",
-  "worker_type": "ui-style",
-  "status": "completed",
-  "ui_analysis_level": "full",
-  "documents_generated": [
-    "ui-style/ui-style-guide.md"
-  ],
-  "analysis_file": "web-vue.analysis-ui-style.json",
-  "completed_at": "2024-01-15T10:45:00Z"
-}
-```
-
-**Status values**:
-- `completed` — All required documents generated successfully
-- `failed` — Critical failure, required documents not generated
-
-If a Worker encounters a fatal error, it should still attempt to create the done file with `status: "failed"` and include error details in an `"error"` field.
-
-#### Quality Worker Done File
-
-**File**: `{completed_dir}/{platform_id}.quality-done.json`
-
-**Format**:
-```json
-{
-  "platform_id": "web-vue",
-  "worker_type": "quality",
-  "status": "completed",
-  "quality_score": 85,
-  "issues_found": 2,
-  "completed_at": "2024-01-15T11:00:00Z"
-}
-```
-
----
-
-### Platform Status Tracking Fields
-
-Each platform entry in techs-manifest.json includes status tracking fields for monitoring the analysis pipeline progress:
-
-| Field | Type | Values | Description |
-|-------|------|--------|-------------|
-| `status` | string | `pending` / `processing` / `completed` / `partial` / `failed` | Current analysis status |
-| `startedAt` | string \| null | ISO 8601 timestamp | When the Worker started analyzing this platform |
-| `completedAt` | string \| null | ISO 8601 timestamp | When the Worker finished analyzing this platform |
-| `analysisLevel` | string \| null | `full` / `minimal` / `reference_only` | Depth of analysis achieved |
-| `topicsCoverage` | number \| null | 0-100 | Percentage of domain topics covered (from analysis.json) |
-| `workers` | object | See below | Per-worker status tracking |
-
-**Workers Object Structure:**
-```json
-{
-  "platform_id": "web-vue",
-  "status": "completed",
-  "workers": {
-    "conventions": {
-      "status": "completed",
-      "skill": "speccrew-knowledge-techs-generate-conventions",
-      "done_file": "web-vue.done-conventions.json"
-    },
-    "ui_style": {
-      "status": "completed",
-      "skill": "speccrew-knowledge-techs-generate-ui-style",
-      "done_file": "web-vue.done-ui-style.json"
-    }
-  }
-}
-```
-
-For backend platforms, `ui_style.status` is set to `"skipped"`.
-
-**Status Lifecycle:**
-```
-pending → processing → completed
-                    → partial (conventions OK, ui-style failed)
-                    → failed
-```
-
----
-
-### Output per Platform
-
-```
-speccrew-workspace/knowledges/techs/{platform_id}/
-├── INDEX.md                    # Required
-├── tech-stack.md              # Required
-├── architecture.md            # Required
-├── conventions-design.md      # Required
-├── conventions-dev.md         # Required
-├── conventions-unit-test.md        # Required
-├── conventions-system-test.md      # Required
-├── conventions-build.md       # Required
-├── conventions-data.md        # Optional — platform-specific
-└── ui-style/                  # Optional — frontend only (web/mobile/desktop)
-    ├── ui-style-guide.md      # Generated by techs Stage 2
-    ├── page-types/            # Populated by bizs pipeline Stage 3.5 (ui-style-extract)
-    ├── components/            # Populated by bizs pipeline Stage 3.5 (ui-style-extract)
-    ├── layouts/               # Populated by bizs pipeline Stage 3.5 (ui-style-extract)
-    └── styles/                # Generated by techs Stage 2
-```
-
-**Cross-Pipeline Note for `ui-style/`**:
-- `ui-style-guide.md` and `styles/` are generated by techs pipeline Stage 2 (technical framework-level style specs)
-- `page-types/`, `components/`, and `layouts/` are populated by bizs pipeline Stage 3.5 (`speccrew-knowledge-bizs-ui-style-extract` skill), which aggregates patterns from analyzed feature documents
-- These two sources are complementary: techs provides framework-level conventions, bizs adds real-page-derived design patterns
-- If bizs pipeline has not been executed, these three subdirectories will be empty
-
-**Optional file `conventions-data.md` rules**:
-
-| Platform Type | Required? | Notes |
-|----------|-----------|-------|
-| `backend` | Required | ORM specs, data modeling, caching |
-| `web` | Depends | Only if using ORM/data layer (Prisma, TypeORM, etc.) |
-| `mobile` | Optional | Based on tech stack |
-| `desktop` | Optional | Based on tech stack |
-
----
-
-### Error Handling
-
-#### Error Handling Strategy
-
-```
-ON Worker Failure:
-  1. Capture error message from worker_result.error
-  2. Mark platform status as "failed" in stage2-status.json
-  3. Record failed platform_id and error details
-  4. Continue processing other platforms (no retry, fail fast)
-  5. After all workers complete, evaluate overall status:
-     - IF all platforms failed → ABORT pipeline
-     - IF some platforms succeeded → CONTINUE to Stage 3 with successful platforms only
-```
-
-#### Stage-Level Failure Handling
-
-| Stage | Failure Handling |
-|-------|-----------------|
-| Stage 1 | Abort pipeline, report error |
-| Stage 2 | Continue with successful platforms, report failed ones |
-| Stage 2.5 | Continue pipeline, report warnings |
-| Stage 3 | Abort if Stage 2 had critical failures |
-
-#### Worker Failure Details
-
-**When a Worker Agent fails:**
-- **No automatic retry**: Worker failures are recorded as-is
-- **Partial success accepted**: Pipeline continues if at least one platform succeeds
-- **Error propagation**: Failed platform details are included in stage2-status.json
-- **Stage 3 decision**: Only platforms with status "complete" are included in root INDEX.md
-
----
-
-### Checklist
-
-- [ ] Stage 1: Platform manifest generated with techs-manifest.json
-- [ ] Stage 2: All platforms processed in parallel
-- [ ] Stage 2: `stage2-status.json` generated with all platform results
-- [ ] Stage 3: Root INDEX.md generated with Agent mapping
-- [ ] Stage 3: `stage3-status.json` generated with index info
-
-#### Document Completeness Verification
-- [ ] Each platform directory contains required documents: INDEX.md, tech-stack.md, architecture.md, conventions-design.md, conventions-dev.md, conventions-unit-test.md, conventions-system-test.md, conventions-build.md
-- [ ] `conventions-data.md` exists only for appropriate platforms (backend required, others optional)
-- [ ] All documents include file reference blocks (pure Markdown format for VS Code preview compatibility)
-- [ ] All documents include AI-TAG and AI-CONTEXT comments
-- [ ] techs/INDEX.md links only to existing documents
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: speccrew-workspace/docs/rules/agentflow-spec.md
+> Then read and execute the XML workflow in SKILL.xml block-by-block as the authoritative execution plan.

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

@@ -4,165 +4,12 @@ description: Stage 2 of technology knowledge initialization - Generate technolog
 tools: Read, Write, Glob, Grep, Skill
 ---
 
-> **⚠️ DEPRECATED**: This skill has been superseded by `speccrew-knowledge-techs-generate-conventions` and `speccrew-knowledge-techs-generate-ui-style`. Use those skills for new requests. This file is kept for backward compatibility only.
->
-> **Do NOT invoke this skill directly.** Use the specialized skills via `speccrew-knowledge-techs-dispatch` Stage 2 dual-worker orchestration.
-
-# Stage 2: Generate Platform Technology Documents (XML Workflow)
-
-Generate comprehensive technology documentation for a specific platform by analyzing its configuration files and source code structure.
-
-## Language Adaptation
-
-**CRITICAL**: Generate all content in the language specified by the `language` parameter.
-
-## Input
-
-- `platform_id`: Platform identifier (e.g., "web-react", "backend-nestjs")
-- `platform_type`: Platform type (web, mobile, backend, desktop)
-- `framework`: Primary framework (react, nestjs, flutter, etc.)
-- `source_path`: Platform source directory
-- `config_files`: List of configuration file paths
-- `convention_files`: List of convention file paths (eslint, prettier, etc.)
-- `output_path`: Output directory for generated documents
-- `language`: Target language (e.g., "zh", "en") - **REQUIRED**
-- `completed_dir`: (Optional) Directory for analysis coverage report output
-
-## Output
-
-**Required Documents (All Platforms)**: INDEX.md, tech-stack.md, architecture.md, conventions-design.md, conventions-dev.md, conventions-unit-test.md, conventions-system-test.md, conventions-build.md
-
-**Optional Documents**: conventions-data.md (backend required), ui-style/ (frontend only)
-
-**Quality Assurance**: After document generation, quality checks are performed by `speccrew-knowledge-techs-generate-quality` skill.
+# Trigger Scenarios
+- "Generate tech docs for {platform}"
+- "Create technology documentation"
+- "Extract tech stack and conventions"
 
 ## AgentFlow Definition
-
 <!-- @agentflow: SKILL.xml -->
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
-
----
-
-## Reference Guides
-
-### Mermaid Diagram Guide
-
-**Key Requirements:** Use basic node definitions only. No HTML tags, no nested subgraphs, no `direction` keyword, no `style` definitions.
-
-**Diagram Types**: `graph TB/LR` (structure), `flowchart TD` (logic), `sequenceDiagram` (interactions), `classDiagram` (classes), `erDiagram` (database), `stateDiagram-v2` (states)
-
-### Source Traceability Requirements
-
-**CRITICAL: All source file links MUST use RELATIVE PATHS.** No absolute paths, no `file://` protocol.
-
-**Relative Path Calculation**: Documents at `speccrew-workspace/knowledges/techs/{platform_id}/` are 4 levels deep. Use `../../../../` prefix to reference project root files.
-
-**Required Elements**:
-1. File reference block at document beginning listing referenced files
-2. `**Diagram Source**` annotation after each Mermaid diagram
-3. `**Section Source**` annotation at end of major sections
-
-### Document Content Specifications
-
-#### INDEX.md
-Platform summary, technology stack overview, navigation links, agent usage guide.
-
-#### tech-stack.md
-Overview, Core Technologies table, Dependencies (grouped), Development Tools, Configuration Files.
-
-#### architecture.md
-**Web**: Component Architecture, State Management, Routing, API Integration, Styling. **Backend**: Layered Architecture, DI, Module Organization, API Design, Middleware. **Mobile**: Widget Structure, State Management, Navigation, Platform considerations.
-
-#### conventions-design.md
-Design Principles (SOLID, DRY), Design Patterns, UI Design Conventions (reference ui-style/), Data Flow, Error Handling, Security, Performance.
-
-#### conventions-dev.md
-Naming Conventions, Directory Structure, Code Style (from ESLint/Prettier), Import/Export Patterns, Git Commit Conventions, Pre-Development Checklist, Code Review Checklist.
-
-**Source extraction**: Prettier (.prettierrc), ESLint (.eslintrc), EditorConfig (.editorconfig), Git hooks (.husky/), Commit conventions (.commitlintrc), Runtime version (.nvmrc), IDE config (.vscode/).
-
-#### conventions-unit-test.md / conventions-system-test.md
-Unit Testing (framework, naming, location, template, run command), Integration Testing, E2E Testing (frontend only), Database Testing (backend only), Performance Testing, Coverage Requirements, Troubleshooting.
-
-#### conventions-build.md
-Build Tool & Configuration, Environment Management, Build Profiles & Outputs, CI/CD (if detected), Docker (if detected), Dependency Management.
-
-#### conventions-data.md (Optional)
-ORM/Database Tool, Data Modeling, Migrations, Query Optimization, Caching.
-
----
-
-## Template Usage
-
-Templates are located at `./templates/`:
-
-| Template File | Purpose |
-|---------------|---------|
-| INDEX-TEMPLATE.md | Platform overview |
-| TECH-STACK-TEMPLATE.md | Technology stack |
-| ARCHITECTURE-TEMPLATE.md | Architecture patterns |
-| CONVENTIONS-DESIGN-TEMPLATE.md | Design principles |
-| CONVENTIONS-DEV-TEMPLATE.md | Development conventions |
-| CONVENTIONS-UNIT-TEST-TEMPLATE.md | Unit testing |
-| CONVENTIONS-SYSTEM-TEST-TEMPLATE.md | System testing |
-| CONVENTIONS-BUILD-TEMPLATE.md | Build/deployment |
-| CONVENTIONS-DATA-TEMPLATE.md | Data layer |
-
-## Checklist
-
-### Pre-Generation
-- [ ] All configuration files read and parsed
-- [ ] Technology stack extracted accurately
-- [ ] Conventions analyzed from config files
-- [ ] Platform type identified
-- [ ] Data layer detection completed for non-backend platforms
-
-### Required Documents (All Platforms)
-- [ ] INDEX.md, tech-stack.md, architecture.md
-- [ ] conventions-design.md, conventions-dev.md
-- [ ] conventions-unit-test.md, conventions-system-test.md, conventions-build.md
-
-### Optional Document
-- [ ] conventions-data.md (if applicable)
-
-### UI Style Analysis (Frontend Platforms)
-- [ ] ui-analyze skill invoked
-- [ ] ui-style-guide.md generated
-- [ ] UI conventions referenced in conventions-design.md
-
-## Task Completion Report
-
-Upon completion, output the following structured report:
-
-```json
-{
-  "status": "success | partial | failed",
-  "skill": "speccrew-knowledge-techs-generate",
-  "output_files": [
-    "{output_path}/INDEX.md",
-    "{output_path}/tech-stack.md",
-    "{output_path}/architecture.md"
-  ],
-  "summary": "Tech documentation generated for {platform_id}",
-  "metrics": {
-    "documents_generated": 0,
-    "sections_filled": 0,
-    "code_examples_included": 0
-  },
-  "errors": [],
-  "next_steps": ["Run quality check via speccrew-knowledge-techs-generate-quality"]
-}
-```
-
----
-
-## CONTINUOUS EXECUTION RULES
-
-This skill follows the continuous execution pattern defined in `GLOBAL-R1`:
-
-1. **Sequential Execution**: All workflow steps must execute in the defined order without interruption.
-2. **No User Prompts**: Worker must not pause for user confirmation between steps.
-3. **Complete All Steps**: Worker must complete all steps before reporting results.
-4. **Error Handling**: If any step fails, continue with remaining steps if possible, then report all errors together.
-5. **Technology Stack Constraint**: Per `GLOBAL-R-TECHSTACK`, all generated documents must align with the detected technology stack.
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: speccrew-workspace/docs/rules/agentflow-spec.md
+> Then read and execute the XML workflow in SKILL.xml block-by-block as the authoritative execution plan.

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

@@ -4,151 +4,12 @@ description: Generate technology convention documents (INDEX, tech-stack, archit
 tools: Read, Write, Glob, Grep
 ---
 
-# Stage 2: Generate Platform Convention Documents (XML Block Workflow)
-
-Generate comprehensive convention documentation for a specific platform by analyzing its configuration files and source code structure. This skill focuses on conventions documents only; UI style analysis is handled by the separate techs-generate-ui-style worker.
-
-## Trigger Scenarios
-
+# Trigger Scenarios
 - "Generate convention documents for {platform}"
 - "Create tech stack and architecture documentation"
 - "Extract development conventions from {platform}"
-- "Generate platform conventions docs"
-- "Create INDEX, tech-stack, and conventions-* files"
-
-## User
-
-Worker Agent (speccrew-task-worker)
-
-## Input Variables
-
-| Variable | Type | Description | Example |
-|----------|------|-------------|---------|
-| `${platform_id}` | string | Platform identifier | `"web-react"`, `"backend-nestjs"` |
-| `${platform_type}` | string | Platform type | `web`, `mobile`, `backend`, `desktop`, `api` |
-| `${framework}` | string | Primary framework | `react`, `nestjs`, `flutter`, etc. |
-| `${source_path}` | string | Platform source directory | `"frontend-web"` |
-| `${config_files}` | array | List of configuration file paths | `["package.json", "tsconfig.json"]` |
-| `${convention_files}` | array | List of convention file paths | `[".eslintrc.js", ".prettierrc"]` |
-| `${output_path}` | string | Output directory for generated documents | `speccrew-workspace/knowledges/techs/{platform_id}/` |
-| `${language}` | string | Target language for generated content | `"zh"`, `"en"` |
-| `${completed_dir}` | string | (Optional) Directory for analysis coverage report output | `speccrew-workspace/iterations/...` |
-
-## Output Variables
-
-| Variable | Type | Description |
-|----------|------|-------------|
-| `${status}` | string | Generation status: `"success"`, `"partial"`, or `"failed"` |
-| `${documents_generated}` | array | List of generated document filenames |
-| `${analysis_file}` | string | Path to the analysis coverage report |
-| `${message}` | string | Summary message for status update |
-
-## Output
-
-Generate the following documents in `${output_path}/`:
-
-```
-${output_path}/
-├── INDEX.md                    # Platform technology index (Required)
-├── tech-stack.md              # Technology stack details (Required)
-├── architecture.md            # Architecture conventions (Required)
-├── conventions-design.md      # Design conventions (Required)
-├── conventions-dev.md         # Development conventions (Required)
-├── conventions-unit-test.md   # Unit testing conventions (Required)
-├── conventions-system-test.md # System testing conventions (Required)
-├── conventions-build.md       # Build & Deployment conventions (Required)
-└── conventions-data.md        # Data conventions (Optional)
-```
-
-### Platform Type to Document Mapping
-
-| Platform Type | Required Documents | Optional Documents | Generate conventions-data.md? |
-|---------------|-------------------|-------------------|------------------------------|
-| `backend` | All 8 docs | - | **Must Generate** - Contains ORM, data modeling, caching strategy |
-| `web` | All 8 docs | conventions-data.md | **Conditional** - Only when using ORM/data layer (Prisma, TypeORM, Sequelize, etc.) |
-| `mobile` | All 8 docs | conventions-data.md | **Default No** - Based on actual tech stack |
-| `desktop` | All 8 docs | conventions-data.md | **Default No** - Based on actual tech stack |
-| `api` | All 8 docs | conventions-data.md | **Conditional** - Based on whether data layer exists |
 
 ## AgentFlow Definition
-
 <!-- @agentflow: SKILL.xml -->
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
-
-
-
-## Constraints
-
-1. **DO NOT create temporary scripts, batch files, or workaround code files (`.py`, `.bat`, `.sh`, `.ps1`, etc.)** under any circumstances
-2. **DO NOT analyze files outside the specified `${source_path}`**
-3. **All content MUST be in the language specified by `${language}`**
-4. **Use `search_replace` for section filling, NEVER rewrite entire document**
-5. **Mermaid diagrams MUST follow the rules in `mermaid-rule.md`**
-6. **All links MUST use relative paths, NEVER `file://` protocol**
-7. **Write each document to file immediately after generation - DO NOT accumulate all documents in memory**
-8. **DO NOT create done marker file until ALL required documents have been verified to exist on disk**
-
-## Task Completion Report
-
-When the task is complete, report the following:
-
-**Status:** `success` | `partial` | `failed`
-
-**Summary:**
-- Platform: `${platform_id}`
-- Type: `${platform_type}`
-- Framework: `${framework}`
-- Documents generated: 8 required + (1 optional if data layer detected)
-
-**Files Generated:**
-- `${output_path}/INDEX.md` - Platform technology index
-- `${output_path}/tech-stack.md` - Technology stack details
-- `${output_path}/architecture.md` - Architecture conventions
-- `${output_path}/conventions-design.md` - Design conventions
-- `${output_path}/conventions-dev.md` - Development conventions
-- `${output_path}/conventions-unit-test.md` - Unit testing conventions
-- `${output_path}/conventions-system-test.md` - System testing conventions
-- `${output_path}/conventions-build.md` - Build and deployment conventions
-- `${output_path}/conventions-data.md` - Data conventions (optional)
-- `${completed_dir}/${platform_id}.analysis-conventions.json` - Analysis coverage report
-
-## Checklist
-
-### Pre-Generation
-- [ ] All template files read successfully
-- [ ] All configuration files read and parsed
-- [ ] Technology stack extracted accurately
-- [ ] Conventions analyzed from config files
-
-### Document Generation
-- [ ] INDEX.md generated with navigation
-- [ ] tech-stack.md generated with dependency tables
-- [ ] architecture.md generated with platform-specific patterns
-- [ ] conventions-design.md generated with design principles
-- [ ] conventions-dev.md generated with naming and style rules
-- [ ] conventions-unit-test.md generated with unit testing requirements
-- [ ] conventions-system-test.md generated with system testing requirements
-- [ ] conventions-build.md generated with build and deployment conventions
-- [ ] conventions-data.md generated (only if applicable per platform type mapping)
-
-### Quality Checks
-- [ ] All files written to output_path
-- [ ] **Source traceability**: File reference block added to each document
-- [ ] **Source traceability**: Diagram Source annotations added after each Mermaid diagram
-- [ ] **Source traceability**: Section Source annotations added at end of major sections
-- [ ] **Mermaid compatibility**: No `style`, `direction`, `<br/>`, or nested subgraphs
-- [ ] **Document completeness**: All 8 required documents exist (verified in Step 3)
-- [ ] **Done marker integrity**: Done marker only created after verification
-- [ ] **Analysis Coverage Report**: `${platform_id}.analysis-conventions.json` generated
-
-## CONTINUOUS EXECUTION RULES
-
-This skill MUST execute continuously without user interruption:
-
-1. **All steps must complete in a single session** - from template reading to done marker creation
-2. **If context window is running low**: Save checkpoint and inform user - DO NOT create false done marker
-3. **No intermediate user confirmation required** between steps
-4. **Error handling**: On error, log details and stop - do not proceed with incomplete data
-5. **Verification gate**: Step 3 verification MUST pass before Step 4 done marker creation
-6. **Memory management**: Write each document immediately after generation, do not accumulate in memory
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: speccrew-workspace/docs/rules/agentflow-spec.md
+> Then read and execute the XML workflow in SKILL.xml block-by-block as the authoritative execution plan.