speccrew 0.7.74 → 0.7.75

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

@@ -4,189 +4,12 @@ description: Generate UI style analysis documents for a specific frontend platfo
 tools: Read, Write, Glob, Grep, Skill
 ---
 
-# Stage 2: Generate Platform UI Style Documents (XML Workflow)
-
-Generate comprehensive UI style documentation for a specific frontend platform by analyzing its source code structure, components, and styling patterns using XML workflow blocks.
-
-## Language Adaptation
-
-**CRITICAL**: All generated documents must match the user's language. Detect the language from the user's input and generate content accordingly.
-
-- User writes in 中文 → Generate Chinese documents, use `language: "zh"`
-- User writes in English → Generate English documents, use `language: "en"`
-- Other languages → Use the specified language code
-
-## Prerequisite
-
-This skill ONLY applies to frontend platforms. The dispatcher MUST check platform_type before invoking:
-
-- `web` → Execute this skill
-- `mobile` → Execute this skill
-- `desktop` → Execute this skill
-- `backend` → DO NOT invoke this skill
-- `api` → DO NOT invoke this skill
-
-## Trigger Scenarios
-
+# Trigger Scenarios
 - "Generate UI style documents for {platform}"
 - "Analyze UI components and layouts"
 - "Extract design system from {platform}"
 
-## User
-
-Worker Agent (speccrew-task-worker)
-
----
-
 ## AgentFlow Definition
-
 <!-- @agentflow: SKILL.xml -->
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
-
----
-
-## Output Directory Structure
-
-```
-{output_path}/
-└── ui-style/
-    ├── ui-style-guide.md              # Main UI style guide (Required)
-    ├── page-types/
-    │   ├── page-type-summary.md       # Page type overview (Required)
-    │   └── [type]-pages.md            # Per-type detail (Dynamic)
-    ├── components/
-    │   ├── component-library.md       # Component catalog (Required)
-    │   ├── common-components.md       # Common components (Required)
-    │   ├── business-components.md     # Business components (Required)
-    │   └── {component-name}.md        # Per-component detail (Dynamic)
-    ├── layouts/
-    │   ├── page-layouts.md            # Layout patterns (Required)
-    │   ├── navigation-patterns.md     # Navigation patterns (Required)
-    │   └── {layout-name}-layout.md    # Per-layout detail (Dynamic)
-    └── styles/
-        ├── color-system.md            # Color system (Required)
-        ├── typography.md              # Typography (Required)
-        └── spacing-system.md          # Spacing system (Required)
-```
-
-## Directory Ownership
-
-- `ui-style/` — Fully managed by this skill (techs pipeline)
-  - Contains: ui-style-guide.md, styles/, page-types/, components/, layouts/
-  - Source: Framework-level design system analysis from source code
-- `ui-style-patterns/` — Managed by bizs pipeline (Stage 3.5: bizs-ui-style-extract)
-  - Contains: Business pattern aggregation from feature documents
-  - NOT created or written by this skill
-  - May not exist if bizs pipeline has not been executed
-
----
-
-## Quality Requirements
-
-- ui-style-guide.md MUST have substantial content (not just template placeholders)
-- At least 5 mandatory files MUST exist (see Self-Verification Checklist)
-- Analysis report MUST honestly reflect coverage level
-- All paths in documents MUST be relative (never absolute or file:// protocol)
-
----
-
-## Error Handling
-
-| Error Type | Action |
-|------------|--------|
-| Platform type is backend/api | Skip execution, return skipped status |
-| UI analyzer skill invocation fails | Execute Secondary Path (template fill) |
-| Source code structure is non-standard | Execute Tertiary Path (reference only) |
-| Template not found | Use default structure, log warning |
-| Any path MUST output the done file and analysis file | Never report "completed" with missing mandatory files |
-
----
-
-## Task Completion Report
-
-Upon completion, return the following structured report:
-
-```json
-{
-  "status": "success | partial | failed",
-  "skill": "speccrew-knowledge-techs-generate-ui-style",
-  "output_files": [
-    "{output_path}/ui-style/ui-style-guide.md",
-    "{output_path}/ui-style/page-types/page-type-summary.md",
-    "{output_path}/ui-style/components/component-library.md",
-    "{output_path}/ui-style/layouts/page-layouts.md",
-    "{output_path}/ui-style/styles/color-system.md",
-    "{completed_dir}/{platform_id}.analysis-ui-style.json",
-    "{completed_dir}/{platform_id}.done-ui-style.json"
-  ],
-  "summary": "UI style documents generated for {platform_id} at {ui_analysis_level} analysis level",
-  "metrics": {
-    "components_documented": 0,
-    "style_patterns_captured": 0,
-    "design_tokens_extracted": 0
-  },
-  "errors": [],
-  "next_steps": [
-    "Review ui-style-guide.md for design system completeness",
-    "Coordinate with bizs-ui-style-extract for business pattern integration"
-  ]
-}
-```
-
----
-
-## Checklist
-
-### Pre-Generation
-- [ ] Platform type verified (web/mobile/desktop only)
-- [ ] Template files read and understood
-- [ ] Source directory structure scanned
-
-### UI Style Analysis
-- [ ] `speccrew-knowledge-techs-ui-analyze` skill invoked (Primary Path)
-- [ ] If Primary Path failed → Secondary Path executed
-- [ ] If Secondary Path failed → Tertiary Path executed
-- [ ] All mandatory files created per Self-Verification Checklist
-
-### Output Verification
-- [ ] ui-style/ui-style-guide.md exists and has content
-- [ ] ui-style/page-types/page-type-summary.md exists and has content
-- [ ] ui-style/components/component-library.md exists and has content
-- [ ] ui-style/layouts/page-layouts.md exists and has content
-- [ ] ui-style/styles/color-system.md exists and has content
-
-### Reporting
-- [ ] Analysis report generated: `{platform_id}.analysis-ui-style.json`
-- [ ] Completion marker generated: `{platform_id}.done-ui-style.json`
-- [ ] Console output reported with correct status
-
----
-
-## CONTINUOUS EXECUTION RULES
-
-This skill MUST execute all steps continuously without unnecessary interruptions.
-
-### FORBIDDEN Interruptions
-
-1. DO NOT ask user "Should I continue?" after completing a step
-2. DO NOT suggest "Let me split this into batches" or "Let's do this in parts"
-3. DO NOT pause to list what you plan to do next — just do it
-4. DO NOT ask for confirmation before generating output files
-5. DO NOT warn about "large number of files" — proceed with generation
-6. DO NOT offer "Should I proceed with the remaining items?"
-7. DO NOT present options like "Full execution / Sample execution / Pause"
-
-### When to Pause (ONLY these cases)
-
-1. Explicit `<event action="confirm">` blocks in the workflow
-2. Ambiguous requirements that genuinely need clarification
-3. Unrecoverable errors that prevent further progress
-4. Security-sensitive operations (e.g., deleting existing files)
-
-### Execution Behavior
-
-- When multiple templates need filling, process ALL of them sequentially without asking
-- Use checkpoint files to track progress, enabling resumption if interrupted
-- If context window is approaching limit, save progress and inform user how to resume
-- NEVER voluntarily stop mid-process to ask if user wants to continue
+> **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-index/SKILL.md

@@ -4,163 +4,12 @@ description: Stage 3 of technology knowledge initialization - Generate root INDE
 tools: Read, Write, Skill
 ---
 
-# Stage 3: Generate Root Technology Index (XML Workflow)
-
-Aggregate all platform technology documentation into a single root INDEX.md that serves as the master navigation hub for technology knowledge.
-
-## Language Adaptation
-
-**CRITICAL**: Generate all content in the language specified by the `language` parameter.
-
-- `language: "zh"` → Generate all content in 中文
-- `language: "en"` → Generate all content in English
-- Other languages → Use the specified language
-
-## Trigger Scenarios
-
+# Trigger Scenarios
 - "Generate techs root index"
 - "Create technology knowledge index"
 - "Aggregate platform tech docs"
-- "Generate master tech index"
-
-## User
-
-Worker Agent (speccrew-task-worker)
-
-## Input
-
-- `manifest_path`: Path to techs-manifest.json
-- `techs_base_path`: Base path for techs documentation (default: `speccrew-workspace/knowledges/techs/`)
-- `output_path`: Output path for root INDEX.md (default: `speccrew-workspace/knowledges/techs/`)
-- `language`: Target language (e.g., "zh", "en") - **REQUIRED**
-
-## Output
-
-- `{{output_path}}/INDEX.md` - Root technology knowledge index
-
-**INDEX.md Content Structure**:
-- Introduction (generation info, platform count)
-- Platform Overview (table with links to all platform docs)
-- Quick Reference (links organized by document type)
-- Agent-to-Platform Mapping (maps agents to their platform docs)
-- Document Guide (explains each document type)
-- Usage Guide (how to use the knowledge)
 
 ## AgentFlow Definition
-
 <!-- @agentflow: SKILL.xml -->
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
-
----
-
-## Template Usage
-
-Templates are located at `./templates/`:
-
-**Template Variables:**
-- `{{generated_at}}`: ISO timestamp
-- `{{source_path}}`: Source path
-- `{{platform_count}}`: Number of platforms
-- `{{#each platforms}}`: Loop through platforms
-  - `{{platform_id}}`: Platform identifier
-  - `{{platform_type}}`: Platform type
-  - `{{framework}}`: Framework name
-  - `{{language}}`: Programming language
-
----
-
-## Document Structure Details
-
-### Section 1: Header
-
-```markdown
-# Technology Knowledge Index
-
-**Files Referenced in This Document**
-
-- [techs-manifest.json](../../../speccrew-workspace/knowledges/techs/techs-manifest.json)
-
-> **Target Audience**: devcrew-designer-*, devcrew-dev-*, devcrew-test-*
-```
-
-### Section 2: Platform Overview
-
-Summary table of all platforms with **dynamically generated document links**:
-
-```markdown
-## Platform Overview
-
-| Platform | Type | Framework | Stack | Arch | Design | Dev | Test | Build | Data |
-|----------|------|-----------|-------|------|--------|-----|------|-------|------|
-| [web-react](web-react/INDEX.md) | web | React | [Stack](web-react/tech-stack.md) | ... | ... | ... | ... | ... | - |
-```
-
-**Dynamic Link Generation Rules:**
-
-1. **Always include links to required documents** (if they exist)
-2. **Conditionally include conventions-data.md**: Show `-` if not exists
-3. **Link Format**: Use short abbreviations to save space
-
-### Section 3: Quick Reference
-
-Quick links organized by document type (Technology Stacks, Architecture Guidelines, Design Conventions, etc.)
-
-### Section 4: Agent-to-Platform Mapping
-
-Critical section that defines how Agents map to platform documentation. **Must dynamically adjust based on actual document availability.**
-
-**Dynamic Adjustment Rules:**
-
-1. **Designer Agent Documents**: Primary + Optional (conventions-data.md, ui-style-patterns/)
-2. **Developer Agent Documents**: Primary (conventions-dev.md, conventions-build.md) + Optional
-3. **Tester Agent Documents**: Primary (conventions-test.md, conventions-build.md) + Optional
-
-### Section 5: Document Guide
-
-Explain what each document type contains.
-
-### Section 6: Usage Guide
-
-How to use the technology knowledge for Designer, Developer, and Tester Agents.
-
----
-
-## Checklist
-
-### Pre-Generation
-- [ ] techs-manifest.json read successfully
-- [ ] Platform list extracted from manifest
-
-### Dynamic Document Detection
-- [ ] Each platform directory scanned for actual document existence
-- [ ] Document availability map created for each platform
-- [ ] Required documents verified
-- [ ] Optional conventions-data.md existence checked per platform
-
-### Content Generation
-- [ ] Platform summaries extracted from existing INDEX.md files
-- [ ] Root INDEX.md generated with all sections
-- [ ] **Platform Overview table**: Links dynamically generated based on actual document existence
-- [ ] **Agent-to-Platform mapping**: Document recommendations adjusted per platform
-- [ ] Document guide included
-- [ ] Usage guide included
-
-### Quality & Validation
-- [ ] No broken links to non-existent documents
-- [ ] conventions-data.md links only included for platforms where it exists
-- [ ] **Source traceability**: File reference block added to root INDEX.md
-- [ ] Output file written successfully
-- [ ] Results reported with document availability summary
-
----
-
-## 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 index documents must accurately reflect detected platform technology stacks.
+> **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-init/SKILL.md

@@ -4,185 +4,12 @@ description: Stage 1 of technology knowledge initialization - Scan source code t
 tools: Read, Write, Glob, Grep, SearchCodebase, Skill
 ---
 
-# Stage 1: Detect Technology Platforms (XML Workflow)
-
-Scan project source code to identify all technology platforms, extract configuration metadata, and generate techs-manifest.json for downstream document generation.
-
-## Language Adaptation
-
-**CRITICAL**: Generate all content in the language specified by the `language` parameter.
-
-- `language: "zh"` → Generate all content in 中文
-- `language: "en"` → Generate all content in English
-- Other languages → Use the specified language
-
-**All output content must be in the target language only.**
-
-## Trigger Scenarios
-
+# Trigger Scenarios
 - "Initialize technology knowledge base"
 - "Scan source code for technology platforms"
 - "Detect tech stacks in project"
-- "Generate techs manifest"
-
-## User
-
-Worker Agent (speccrew-task-worker)
-
-## Input
-
-- `source_path`: Source code root directory (default: project root)
-- `output_path`: Output directory for techs-manifest.json (default: `speccrew-workspace/knowledges/base/sync-state/knowledge-techs/`)
-- `language`: Target language for generated content (e.g., "zh", "en") - **REQUIRED**
-
-## Output
-
-- `{{output_path}}/techs-manifest.json` - Technology platform manifest for pipeline orchestration
 
 ## AgentFlow Definition
-
 <!-- @agentflow: SKILL.xml -->
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
-
----
-
-## Platform Detection Reference
-
-### Web Platform Detection
-
-**Indicators:**
-
-| Signal | Platform ID | Framework |
-|--------|-------------|-----------|
-| package.json + react dependency | web-react | React |
-| package.json + vue dependency | web-vue | Vue |
-| package.json + @angular/core | web-angular | Angular |
-| package.json + next | web-nextjs | Next.js |
-| package.json + nuxt | web-nuxt | Nuxt |
-| package.json + svelte | web-svelte | Svelte |
-
-**Configuration Files to Capture:**
-- package.json
-- tsconfig.json
-- vite.config.* / webpack.config.* / next.config.* / nuxt.config.*
-- tailwind.config.* / postcss.config.*
-- .eslintrc.* / .prettierrc.*
-
-### Mobile Platform Detection
-
-**Indicators:**
-
-| Signal | Platform ID | Framework |
-|--------|-------------|-----------|
-| pubspec.yaml | mobile-flutter | Flutter |
-| package.json + react-native | mobile-react-native | React Native |
-| .xcodeproj / Package.swift | mobile-ios | iOS (Swift) |
-| build.gradle + AndroidManifest.xml | mobile-android | Android (Kotlin/Java) |
-| manifest.json + pages.json (uni-app) | mobile-uniapp | UniApp |
-| project.config.json + app.json | mobile-miniprogram | Mini Program |
-
-**Configuration Files to Capture:**
-- Flutter: pubspec.yaml, analysis_options.yaml
-- React Native: package.json, metro.config.js
-- iOS: Package.swift, Podfile, Info.plist
-- Android: build.gradle, AndroidManifest.xml
-
-### Backend Platform Detection
-
-**Indicators:**
-
-| Signal | Platform ID | Framework |
-|--------|-------------|-----------|
-| package.json + @nestjs/core | backend-nestjs | NestJS |
-| package.json + express | backend-express | Express |
-| package.json + fastify | backend-fastify | Fastify |
-| pom.xml + spring-boot | backend-spring | Spring Boot |
-| build.gradle + spring-boot | backend-spring | Spring Boot |
-| requirements.txt + django | backend-django | Django |
-| requirements.txt + fastapi | backend-fastapi | FastAPI |
-| go.mod | backend-go | Go |
-| Cargo.toml | backend-rust | Rust (Actix/Rocket) |
-
-**Configuration Files to Capture:**
-- Node.js: package.json, tsconfig.json, nest-cli.json
-- Java: pom.xml, build.gradle, application.yml/properties
-- Python: requirements.txt, pyproject.toml
-- Go: go.mod, go.sum
-- Rust: Cargo.toml
-
-### Desktop Platform Detection
-
-**Indicators:**
-
-| Signal | Platform ID | Framework |
-|--------|-------------|-----------|
-| package.json + electron | desktop-electron | Electron |
-| tauri.conf.json | desktop-tauri | Tauri |
-| .csproj + WPF references | desktop-wpf | WPF |
-| .csproj + WinForms | desktop-winforms | WinForms |
-| .pro file + Qt | desktop-qt | Qt |
-
-**Configuration Files to Capture:**
-- Electron: package.json, electron-builder.yml
-- Tauri: tauri.conf.json, Cargo.toml
-- WPF/WinForms: .csproj, App.xaml
-- Qt: .pro, CMakeLists.txt
-
----
-
-## Metadata Extraction Fields
-
-| Field | Source | Example |
-|-------|--------|---------|
-| platform_id | `{{platform_type}}-{{framework}}` | web-react, backend-nestjs |
-| platform_type | Platform category | web, mobile, backend, desktop |
-| framework | Primary framework | react, nestjs, flutter |
-| language | Primary language | typescript, kotlin, dart |
-| source_path | Relative source directory | src/web, src/server |
-| config_files | List of config file paths | ["package.json", "tsconfig.json"] |
-| convention_files | Lint/format config files | [".eslintrc.js", ".prettierrc"] |
-
----
-
-## Platform Mapping Consistency
-
-Ensure consistency with modules.json by using standardized platform identifiers from `platform-mapping.json`:
-
-**Key Rules:**
-- `platform_id` format: `{{platform_type}}-{{framework}}` (e.g., `mobile-uniapp`, `web-vue`)
-- `platform_type` must match between techs-manifest.json and modules.json
-- `framework` maps to `platform_subtype` in modules.json
-
-**Example Mapping:**
-
-| platform_id | platform_type | framework | platform_subtype (for bizs-init) |
-|-------------|---------------|-----------|----------------------------------|
-| web-vue | web | vue | vue |
-| mobile-uniapp | mobile | uniapp | uniapp |
-| backend-spring | backend | spring | spring |
-
----
-
-## Checklist
-
-- [ ] All platform indicators checked
-- [ ] Platform metadata extracted (platform_id, type, framework, language)
-- [ ] Configuration files identified and paths recorded
-- [ ] Convention files (eslint, prettier) identified
-- [ ] techs-manifest.json generated with valid JSON structure
-- [ ] **Source traceability**: All config_file paths recorded for downstream use
-- [ ] Output path verified
-- [ ] Results reported with platform summary
-
----
-
-## 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`, detected platforms must align with standardized platform identifiers from platform-mapping.json.
+> **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-ui-analyze/SKILL.md

@@ -4,144 +4,12 @@ description: Analyze existing frontend UI codebase to extract and summarize page
 tools: Read, Write, Glob, Grep
 ---
 
-# UI Style Analyzer
-
-Analyze existing frontend UI codebase to extract and summarize page styles, layout patterns, and component usage for each platform.
-
-## Language Adaptation
-
-**CRITICAL**: Generate all content in the language specified by the `language` parameter.
-
-- `language: "zh"` → Generate all content in 中文
-- `language: "en"` → Generate all content in English
-
-## Trigger Scenarios
-
+# Trigger Scenarios
 - "Analyze UI styles from existing codebase"
 - "Extract page layout patterns from {platform}"
 - "Summarize component usage in {project}"
-- "Generate UI style guide from source code"
-- "梳理现有系统页面风格"
-- "分析项目UI组件使用规范"
-
-## User
-
-Worker Agent (speccrew-task-worker)
-
-## Input
-
-- `source_path`: Path to UI source code directory (e.g., `yudao-ui/yudao-ui-admin-vue3/`)
-- `platform_id`: Platform identifier (e.g., "admin-pc", "admin-mobile")
-- `platform_type`: Platform type (`web`, `mobile`, `desktop`)
-- `framework`: Frontend framework (vue3, react, uniapp, etc.)
-- `output_path`: Output directory for generated style guide
-- `language`: Target language (e.g., "zh", "en") - **REQUIRED**
-
-## Output
-
-Generate the following documents in `{output_path}/`:
-
-**Note**: The `output_path` parameter should already include the `ui-style/` suffix when passed from the caller (e.g., `speccrew-knowledge-techs-generate`).
-
-```
-{output_path}/                    # e.g., .../techs/mobile-uniapp/ui-style/
-├── ui-style-guide.md              # Main UI style guide (Required)
-├── page-types/                    # Page type analysis
-│   ├── page-type-summary.md      # Page type overview (dynamically generated type list)
-│   ├── [type-1]-pages.md         # Specific page type analysis (dynamically named)
-│   ├── [type-2]-pages.md         # Specific page type analysis
-│   └── ...                       # Other discovered page types
-├── components/                    # Component analysis
-│   ├── component-library.md      # Component inventory (summary)
-│   ├── common-components.md      # Common component usage conventions
-│   ├── business-components.md    # Business component usage conventions
-│   └── {component-name}.md       # Individual component detail (one per discovered component)
-├── layouts/                       # Layout patterns
-│   ├── page-layouts.md           # Layout patterns summary
-│   ├── navigation-patterns.md    # Navigation patterns
-│   └── {layout-name}-layout.md   # Individual layout detail (one per discovered layout)
-└── styles/                        # Styling conventions
-    ├── color-system.md           # Color system
-    ├── typography.md             # Typography conventions
-    └── spacing-system.md         # Spacing system
-```
-
-**Note**: Page type documents are dynamically named based on discovered types, e.g.
-- If system has `*List.vue` files → `list-pages.md`
-- If system has `*Form.vue` files → `form-pages.md`
-- If system has `*Dashboard.vue` files → `dashboard-pages.md`
-- If system has custom patterns like `*Workflow.vue` → `workflow-pages.md`
 
 ## AgentFlow Definition
-
 <!-- @agentflow: SKILL.xml -->
-
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
-
-## Checklist
-
-### Pre-Analysis (Step 0)
-- [ ] All 13 templates read and understood
-- [ ] Template section requirements mapped to extraction tasks
-- [ ] Source path exists and accessible
-- [ ] Framework identified (Vue3, React, etc.)
-- [ ] Platform type determined
-
-### Analysis Phase
-**Step 1: Source Structure**
-- [ ] Project structure explored
-- [ ] Technology stack extracted for ui-style-guide.md
-- [ ] Directory structure documented
-
-**Step 2: Page Types**
-- [ ] PAGE-TYPE-SUMMARY-TEMPLATE.md read
-- [ ] PAGE-TYPE-INDIVIDUAL-TEMPLATE.md read
-- [ ] Page files discovered and categorized
-- [ ] page-type-summary.md generated
-- [ ] Individual [type]-pages.md generated (one per discovered type)
-
-**Step 3: Component Usage**
-- [ ] COMPONENT-LIBRARY-TEMPLATE.md read
-- [ ] COMMON-COMPONENTS-TEMPLATE.md read
-- [ ] BUSINESS-COMPONENTS-TEMPLATE.md read
-- [ ] COMPONENT-INDIVIDUAL-TEMPLATE.md read
-- [ ] Components extracted and classified
-- [ ] component-library.md generated
-- [ ] common-components.md generated
-- [ ] business-components.md generated
-- [ ] Individual {component-name}.md files generated (one per discovered component)
-
-**Step 4: Layout Patterns**
-- [ ] LAYOUT-PATTERNS-TEMPLATE.md read
-- [ ] NAVIGATION-PATTERNS-TEMPLATE.md read
-- [ ] LAYOUT-INDIVIDUAL-TEMPLATE.md read
-- [ ] Layout patterns identified
-- [ ] page-layouts.md generated
-- [ ] navigation-patterns.md generated
-- [ ] Individual {layout-name}-layout.md files generated (one per discovered layout)
-
-**Step 5: Style Conventions**
-- [ ] STYLE-SYSTEM-TEMPLATE.md read
-- [ ] TYPOGRAPHY-TEMPLATE.md read
-- [ ] SPACING-TEMPLATE.md read
-- [ ] Style conventions extracted
-- [ ] color-system.md generated
-- [ ] typography.md generated
-- [ ] spacing-system.md generated
-
-### Documentation Phase (Step 6)
-- [ ] UI-STYLE-GUIDE-TEMPLATE.md read
-- [ ] ui-style-guide.md generated with links to all other documents
-- [ ] All 13 required documents exist (11 base + individual component/layout files)
-- [ ] Each component in component-library.md links to its individual file
-- [ ] Each layout in page-layouts.md links to its individual file
-- [ ] Document cross-references are valid
-
-### Quality Checks
-- [ ] All content in specified language
-- [ ] File paths are correct and accessible
-- [ ] Code examples are syntactically correct
-- [ ] ASCII diagrams are clear and accurate
-- [ ] Individual component files follow template structure (Props table, Usage examples, etc.)
-- [ ] Individual layout files follow template structure (Regions table, Navigation, etc.)
-- [ ] Results reported with file counts
+> **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.