speccrew 0.6.69 → 0.7.0

package/.speccrew/skills/{speccrew-knowledge-techs-generate-ui-style-xml/SKILL.md → speccrew-knowledge-techs-generate-ui-style/workflow.agentflow.xml}

@@ -1,46 +1,3 @@
----
-name: speccrew-knowledge-techs-generate-ui-style-xml
-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
----
-
-# 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
-
-- "Generate UI style documents for {platform}"
-- "Analyze UI components and layouts"
-- "Extract design system from {platform}"
-
-## User
-
-Worker Agent (speccrew-task-worker)
-
----
-
-## XML Workflow Definition
-> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
-```xml
 <?xml version="1.0" encoding="UTF-8"?>
 <workflow id="techs-ui-style-generate" status="pending" version="1.0" desc="Generate UI style documents for frontend platform">
   
@@ -259,8 +216,8 @@ Worker Agent (speccrew-task-worker)
             <field name="output_file" value="${output_path}/ui-style/ui-style-guide.md"/>
             <field name="content"># UI Style Guide - ${platform_id}
 
-> Note: Automated and manual UI analysis were not possible for this platform.
-> Manual inspection of source code is required.
+&gt; Note: Automated and manual UI analysis were not possible for this platform.
+&gt; Manual inspection of source code is required.
 
 ## References
 - Source components: ${source_path}/src/components/ (if exists)
@@ -407,151 +364,3 @@ Worker Agent (speccrew-task-worker)
   </block>
 
 </workflow>
-```
-
----
-
-## 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-xml",
-  "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

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

@@ -1,10 +1,10 @@
 ---
 name: speccrew-knowledge-techs-index
-description: Stage 3 of technology knowledge initialization - Generate root INDEX.md by aggregating all platform technology documents. 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.
+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
 ---
 
-# Stage 3: Generate Root Technology Index
+# 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.
 
@@ -46,126 +46,33 @@ Worker Agent (speccrew-task-worker)
 - Document Guide (explains each document type)
 - Usage Guide (how to use the knowledge)
 
-## Workflow
-
-```mermaid
-flowchart TD
-    Start([Start]) --> Step0[Step 0: Read Root Index Template]
-    Step0 --> Step1[Step 1: Read Manifest]
-    Step1 --> Step2[Step 2: Verify Platform Documents]
-    Step2 --> Step3[Step 3: Extract Platform Summaries]
-    Step3 --> Step4[Step 4: Generate Root INDEX.md]
-    Step4 --> Step5[Step 5: Write Output]
-    Step5 --> Step6[Step 6: Report Results]
-    Step6 --> End([End])
-```
-
-### Step 0: Read Root Index Template
-
-Before processing, read the template file to understand the required content structure:
-- **Read**: `templates/INDEX-TEMPLATE.md`
-- **Purpose**: Understand the template chapters and example content requirements for root technology index documents
-- **Key sections to follow**:
-  - Introduction (generation info, platform count)
-  - Project Structure (Platform Overview table, Directory Structure)
-  - Core Components (Technology Stacks, Architecture Guidelines, Design Conventions, Development Conventions, Testing Conventions)
-  - Architecture Overview (Platform Architecture Map with Mermaid diagram)
-  - Detailed Component Analysis (Agent-to-Platform Mapping)
-  - Dependency Analysis (Cross-Platform Dependencies with Mermaid diagram)
-  - Performance Considerations
-  - Troubleshooting Guide
-  - Conclusion
-  - Appendix (Document Guide, Usage Guide)
-
-### Step 1: Read Manifest
-
-Read `techs-manifest.json` to get the list of all platforms:
-
-```json
-{
-  "generated_at": "2024-01-15T10:30:00Z",
-  "source_path": "/project",
-  "language": "zh",
-  "platforms": [
-    {
-      "platform_id": "web-react",
-      "platform_type": "web",
-      "framework": "react",
-      "language": "typescript"
-    },
-    {
-      "platform_id": "backend-nestjs",
-      "platform_type": "backend",
-      "framework": "nestjs",
-      "language": "typescript"
-    }
-  ]
-}
-```
-
-### Step 2: Verify Platform Documents
-
-**CRITICAL**: Do NOT assume all platforms have the same document set. Must dynamically detect which documents actually exist.
-
-**Step 2a: Scan Platform Directories**
-
-For each platform in manifest:
-1. List all `.md` files in `{{techs_base_path}}/{{platform_id}}/`
-2. Build a document availability map for each platform
-
-**Step 2b: Verify Required Documents**
-
-Check each platform for required documents:
-| Document | Required? | If Missing |
-|----------|-----------|------------|
-| INDEX.md | YES | Skip entire platform from root INDEX |
-| tech-stack.md | YES | Mark as "[Missing]" in links |
-| architecture.md | YES | Mark as "[Missing]" in links |
-| conventions-design.md | YES | Mark as "[Missing]" in links |
-| conventions-dev.md | YES | Mark as "[Missing]" in links |
-| conventions-test.md | YES | Mark as "[Missing]" in links |
-| conventions-build.md | YES | Mark as "[Missing]" in links |
-| conventions-data.md | NO | Silently skip link |
-
-**Step 2c: Determine Platform Eligibility**
-
-- IF `INDEX.md` missing → Platform SKIPPED entirely
-- IF any required doc missing (except INDEX.md) → Platform INCLUDED but marked INCOMPLETE
-- IF only conventions-data.md missing → Platform is COMPLETE (it's optional)
+## AgentFlow Definition
 
-### Step 3: Extract Platform Summaries
+<!-- @agentflow: workflow.agentflow.xml -->
 
-Read each platform's INDEX.md to extract:
-- Platform name/type
-- Framework and version
-- Primary language
-- Key technologies (brief)
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
-### Step 4: Generate Root INDEX.md (MANDATORY: Copy Template + Fill)
-
-**CRITICAL**: This step MUST follow the template fill workflow - copy template first, then fill sections.
+---
 
-1. **Copy Template File**:
-   - Copy `templates/INDEX-TEMPLATE.md` to `{output_path}/INDEX.md`
-   - This preserves the template structure and all required sections
+## Template Usage
 
-2. **Fill Template Sections with search_replace**:
-   - Use `search_replace` tool to fill each section of the template
-   - Replace placeholder content with actual data from platform analysis
+Templates are located at `./templates/`:
 
-   **MANDATORY RULES**:
-   - **Do NOT use create_file to rewrite the entire document**
-   - **Do NOT delete or skip any template section**
-   - Only replace the placeholder content within each section
-   - Preserve all template section headers and structure
+**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
 
-3. **Get Timestamp**:
-   - **CRITICAL**: Run `node scripts/get-timestamp.js` to get current timestamp (no format parameter needed, uses default)
-   - Store the output as `{{generated_at}}` template variable
+---
 
-4. **Fill the following sections** in the copied template:
+## Document Structure Details
 
-#### Section 1: Header
+### Section 1: Header
 
 ```markdown
 # Technology Knowledge Index
@@ -175,30 +82,9 @@ Read each platform's INDEX.md to extract:
 - [techs-manifest.json](../../../speccrew-workspace/knowledges/techs/techs-manifest.json)
 
 > **Target Audience**: devcrew-designer-*, devcrew-dev-*, devcrew-test-*
-
-## Table of Contents
-
-1. [Introduction](#introduction)
-2. [Project Structure](#project-structure)
-3. [Core Components](#core-components)
-4. [Architecture Overview](#architecture-overview)
-5. [Detailed Component Analysis](#detailed-component-analysis)
-6. [Dependency Analysis](#dependency-analysis)
-7. [Performance Considerations](#performance-considerations)
-8. [Troubleshooting Guide](#troubleshooting-guide)
-9. [Conclusion](#conclusion)
-10. [Appendix](#appendix)
-
-## Introduction
-
-This technology knowledge index serves all platforms in the project, providing platform overview, document navigation, and Agent usage guidelines.
-
-> Generated at: {{generated_at}}
-> Source: {{source_path}}
-> Platforms: {{platform_count}}
 ```
 
-#### Section 2: Platform Overview
+### Section 2: Platform Overview
 
 Summary table of all platforms with **dynamically generated document links**:
 
@@ -207,220 +93,38 @@ Summary table of all platforms with **dynamically generated document links**:
 
 | Platform | Type | Framework | Stack | Arch | Design | Dev | Test | Build | Data |
 |----------|------|-----------|-------|------|--------|-----|------|-------|------|
-| [web-react](web-react/INDEX.md) | web | React | [Stack](web-react/tech-stack.md) | [Arch](web-react/architecture.md) | [Design](web-react/conventions-design.md) | [Dev](web-react/conventions-dev.md) | [Test](web-react/conventions-test.md) | [Build](web-react/conventions-build.md) | - |
-| [backend-nestjs](backend-nestjs/INDEX.md) | backend | NestJS | [Stack](backend-nestjs/tech-stack.md) | [Arch](backend-nestjs/architecture.md) | [Design](backend-nestjs/conventions-design.md) | [Dev](backend-nestjs/conventions-dev.md) | [Test](backend-nestjs/conventions-test.md) | [Build](backend-nestjs/conventions-build.md) | [Data](backend-nestjs/conventions-data.md) |
-| [mobile-uniapp](mobile-uniapp/INDEX.md) | mobile | UniApp | [Stack](mobile-uniapp/tech-stack.md) | [Arch](mobile-uniapp/architecture.md) | [Design](mobile-uniapp/conventions-design.md) | [Dev](mobile-uniapp/conventions-dev.md) | [Test](mobile-uniapp/conventions-test.md) | [Build](mobile-uniapp/conventions-build.md) | - |
+| [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):
-   - INDEX.md, tech-stack.md, architecture.md, conventions-design.md, conventions-dev.md, conventions-test.md, conventions-build.md
-   - If document missing → Display `[Missing]` instead of link
+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
 
-2. **Conditionally include conventions-data.md**:
-   - If exists → Add link `[Data](...)`
-   - If not exists → Display `-` (dash, not [Missing])
-   - For `backend` platforms, typically include
-   - For `mobile` platforms without data layer, omit
-
-3. **Link Format**: Use short abbreviations to save space:
-   - `[Stack]` → tech-stack.md
-   - `[Arch]` → architecture.md
-   - `[Design]` → conventions-design.md
-   - `[Dev]` → conventions-dev.md
-   - `[Test]` → conventions-test.md
-   - `[Build]` → conventions-build.md (Required column)
-   - `[Data]` → conventions-data.md (Optional column, show `-` if missing)
-
-#### Section 3: Quick Reference
-
-Quick links organized by document type:
-
-```markdown
-## Quick Reference
+### Section 3: Quick Reference
 
-### Technology Stacks
-- [Web Frontend - React](web-react/tech-stack.md)
-- [Backend API - NestJS](backend-nestjs/tech-stack.md)
+Quick links organized by document type (Technology Stacks, Architecture Guidelines, Design Conventions, etc.)
 
-### Architecture Guidelines
-- [Web Frontend](web-react/architecture.md)
-- [Backend API](backend-nestjs/architecture.md)
+### Section 4: Agent-to-Platform Mapping
 
-### Design Conventions
-- [Web Frontend](web-react/conventions-design.md)
-- [Backend API](backend-nestjs/conventions-design.md)
-
-### Development Conventions
-- [Web Frontend](web-react/conventions-dev.md)
-- [Backend API](backend-nestjs/conventions-dev.md)
-
-### Testing Conventions
-- [Web Frontend](web-react/conventions-test.md)
-- [Backend API](backend-nestjs/conventions-test.md)
-```
-
-#### Section 4: Agent-to-Platform Mapping
-
-Critical section that defines how Agents map to platform documentation. **Must dynamically adjust based on actual document availability**:
-
-```markdown
-## Agent-to-Platform Mapping
-
-This section maps dynamically generated Agents to their respective platform documentation.
-
-### Web Frontend (web-react)
-
-| Agent Role | Agent Name | Documentation Path |
-|------------|------------|-------------------|
-| Designer | speccrew-designer-web-react | [speccrew-workspace/knowledges/techs/web-react/](web-react/) |
-| Developer | speccrew-dev-web-react | [speccrew-workspace/knowledges/techs/web-react/](web-react/) |
-| Tester | speccrew-test-web-react | [speccrew-workspace/knowledges/techs/web-react/](web-react/) |
-
-**Key Documents for Web Agents:**
-- Designer: [architecture.md](web-react/architecture.md), [conventions-design.md](web-react/conventions-design.md), [ui-style/ui-style-guide.md](web-react/ui-style/ui-style-guide.md)
-  - If bizs pipeline executed: Also reference [ui-style-patterns/](web-react/ui-style-patterns/) for business UI patterns
-- Developer: [conventions-dev.md](web-react/conventions-dev.md), [conventions-build.md](web-react/conventions-build.md)
-- Tester: [conventions-test.md](web-react/conventions-test.md), [conventions-build.md](web-react/conventions-build.md)
-
-### Backend API (backend-nestjs)
-
-| Agent Role | Agent Name | Documentation Path |
-|------------|------------|-------------------|
-| Designer | speccrew-designer-backend-nestjs | [speccrew-workspace/knowledges/techs/backend-nestjs/](backend-nestjs/) |
-| Developer | speccrew-dev-backend-nestjs | [speccrew-workspace/knowledges/techs/backend-nestjs/](backend-nestjs/) |
-| Tester | speccrew-test-backend-nestjs | [speccrew-workspace/knowledges/techs/backend-nestjs/](backend-nestjs/) |
-
-**Key Documents for Backend Agents:**
-- Designer: [architecture.md](backend-nestjs/architecture.md), [conventions-design.md](backend-nestjs/conventions-design.md), [conventions-data.md](backend-nestjs/conventions-data.md)
-- Developer: [conventions-dev.md](backend-nestjs/conventions-dev.md), [conventions-build.md](backend-nestjs/conventions-build.md), [conventions-data.md](backend-nestjs/conventions-data.md)
-- Tester: [conventions-test.md](backend-nestjs/conventions-test.md), [conventions-build.md](backend-nestjs/conventions-build.md)
-
-### Mobile App (mobile-uniapp) - Example without conventions-data.md
-
-| Agent Role | Agent Name | Documentation Path |
-|------------|------------|-------------------|
-| Designer | speccrew-designer-mobile-uniapp | [speccrew-workspace/knowledges/techs/mobile-uniapp/](mobile-uniapp/) |
-| Developer | speccrew-dev-mobile-uniapp | [speccrew-workspace/knowledges/techs/mobile-uniapp/](mobile-uniapp/) |
-| Tester | speccrew-test-mobile-uniapp | [speccrew-workspace/knowledges/techs/mobile-uniapp/](mobile-uniapp/) |
-
-**Key Documents for Mobile Agents:**
-- Designer: [architecture.md](mobile-uniapp/architecture.md), [conventions-design.md](mobile-uniapp/conventions-design.md), [ui-style/ui-style-guide.md](mobile-uniapp/ui-style/ui-style-guide.md)
-  - If bizs pipeline executed: Also reference [ui-style-patterns/](mobile-uniapp/ui-style-patterns/) for business UI patterns
-- Developer: [conventions-dev.md](mobile-uniapp/conventions-dev.md), [conventions-build.md](mobile-uniapp/conventions-build.md)
-- Tester: [conventions-test.md](mobile-uniapp/conventions-test.md), [conventions-build.md](mobile-uniapp/conventions-build.md)
-```
+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: architecture.md, conventions-design.md, ui-style/ui-style-guide.md
-   - Optional: conventions-data.md (if data layer involved)
-   - Optional: ui-style-patterns/ directory (if bizs pipeline Stage 3.5 executed)
-   - Note: For frontend/mobile platforms, Designer should reference both ui-style/ (tech perspective) and ui-style-patterns/ (business perspective, if exists)
-
-2. **Developer Agent Documents**:
-   - Primary: conventions-dev.md, conventions-build.md
-   - Optional: conventions-data.md
-   - Note: Developer needs conventions-build.md for build process, environment configuration, and CI/CD conventions
-
-3. **Tester Agent Documents**:
-   - Primary: conventions-test.md, conventions-build.md
-   - Optional: conventions-data.md (for database testing)
-   - Note: Tester needs conventions-build.md for CI/CD pipeline and test environment configuration
+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
 
-**UI Style Directory Reference Guide**:
+### Section 5: Document Guide
 
-For frontend platforms (web, mobile, desktop), the INDEX.md should document both UI style directories:
+Explain what each document type contains.
 
-| Directory | Managed By | Content | Reference Condition |
-|-----------|------------|---------|---------------------|
-| `ui-style/` | techs pipeline Stage 2 | Framework-level design system | Always reference for frontend platforms |
-| `ui-style-patterns/` | bizs pipeline Stage 3.5 | Business UI patterns | Only reference if directory exists |
+### Section 6: Usage Guide
 
-#### Section 5: Document Guide
+How to use the technology knowledge for Designer, Developer, and Tester Agents.
 
-Explain what each document type contains:
-
-```markdown
-## Document Guide
-
-### INDEX.md (per platform)
-Platform-specific overview and navigation.
-
-### tech-stack.md
-Framework versions, dependencies, build tools, and configuration files.
-
-### architecture.md
-Architecture patterns, layering, component organization, and design patterns.
-
-### conventions-design.md
-Design principles, patterns, and guidelines for detailed design work.
-
-### conventions-dev.md
-Naming conventions, code style, directory structure, and Git conventions.
-
-### conventions-test.md
-Testing frameworks, coverage requirements, and testing patterns.
-
-### conventions-build.md
-Build process, environment configuration, CI/CD pipelines, and deployment conventions.
-
-### conventions-data.md
-Data modeling, ORM usage, and database conventions (if applicable).
-```
-
-#### Section 6: Usage Guide
-
-How to use the technology knowledge:
-
-```markdown
-## Usage Guide
-
-### For Designer Agents
-1. Read [architecture.md] for platform architecture patterns
-2. Read [conventions-design.md] for design principles
-3. Reference [tech-stack.md] for technology capabilities
-
-### For Developer Agents
-1. Read [conventions-dev.md] for coding standards
-2. Read [conventions-test.md] for testing requirements
-3. Reference [architecture.md] when implementation details are unclear
-
-### For Tester Agents
-1. Read [conventions-test.md] for testing standards
-2. Reference [conventions-design.md] to understand design intent
-```
-
-### Step 5: Write Output
-
-Write the generated INDEX.md to `{{output_path}}/INDEX.md`.
-
-### Step 6: Report Results
-
-```
-Stage 3 completed: Root Technology Index Generated
-- Platforms Indexed: {{platform_count}}
-  - web-react: ✓
-  - backend-nestjs: ✓
-- Root Index: {{output_path}}/INDEX.md
-- Agent Mappings: Documented for all platforms
-```
-
-## Template
-
-Use template at `templates/INDEX-TEMPLATE.md`:
-
-**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
+---
 
 ## Checklist
 
@@ -431,7 +135,7 @@ Use template at `templates/INDEX-TEMPLATE.md`:
 ### Dynamic Document Detection
 - [ ] Each platform directory scanned for actual document existence
 - [ ] Document availability map created for each platform
-- [ ] Required documents verified (INDEX.md, tech-stack.md, architecture.md, conventions-design.md, conventions-dev.md, conventions-test.md, conventions-build.md)
+- [ ] Required documents verified
 - [ ] Optional conventions-data.md existence checked per platform
 
 ### Content Generation
@@ -446,7 +150,17 @@ Use template at `templates/INDEX-TEMPLATE.md`:
 - [ ] 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
-- [ ] **Source traceability**: Section Source annotations added at end of major sections
 - [ ] 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.