speccrew 0.6.69 → 0.7.1

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

@@ -1,56 +1,3 @@
----
-name: speccrew-knowledge-techs-index-xml
-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 (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
-
-- "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)
-
-## Workflow
-
-> **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-index-main" status="pending" version="1.0" desc="Root technology index generation from platform manifests">
 
@@ -205,117 +152,3 @@ Worker Agent (speccrew-task-worker)
   </block>
 
 </workflow>
-```
-
----
-
-## Template Usage
-
-Templates are located at `../speccrew-knowledge-techs-index/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.

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

@@ -1,10 +1,10 @@
 ---
 name: speccrew-knowledge-techs-init
-description: Stage 1 of technology knowledge initialization - Scan source code to detect technology platforms and generate techs-manifest.json. Identifies web, mobile, backend, and desktop platforms by analyzing configuration files and project structure. Used by Worker Agent to kick off the techs pipeline.
+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
 ---
 
-# Stage 1: Detect Technology Platforms
+# 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.
 
@@ -39,26 +39,17 @@ Worker Agent (speccrew-task-worker)
 
 - `{{output_path}}/techs-manifest.json` - Technology platform manifest for pipeline orchestration
 
-## Workflow
+## AgentFlow Definition
 
-```mermaid
-flowchart TD
-    Start([Start]) --> Step1[Step 1: Scan for Platform Indicators]
-    Step1 --> Step2[Step 2: Extract Platform Metadata]
-    Step2 --> Step3[Step 3: Generate techs-manifest.json]
-    Step3 --> Step4[Step 4: Report Results]
-    Step4 --> End([End])
-```
+<!-- @agentflow: workflow.agentflow.xml -->
 
-### Step 1: Scan for Platform Indicators
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
-1. **Read Configuration**:
-   - Read `speccrew-workspace/docs/configs/platform-mapping.json` - Get standardized platform identifiers and mapping rules
+---
 
-2. **Analyze project structure to detect technology platforms**:
-   - Check for platform-specific files and configurations (see [Platform Detection Reference](#platform-detection-reference))
+## Platform Detection Reference
 
-#### Web Platform Detection
+### Web Platform Detection
 
 **Indicators:**
 
@@ -78,7 +69,7 @@ flowchart TD
 - tailwind.config.* / postcss.config.*
 - .eslintrc.* / .prettierrc.*
 
-#### Mobile Platform Detection
+### Mobile Platform Detection
 
 **Indicators:**
 
@@ -97,7 +88,7 @@ flowchart TD
 - iOS: Package.swift, Podfile, Info.plist
 - Android: build.gradle, AndroidManifest.xml
 
-#### Backend Platform Detection
+### Backend Platform Detection
 
 **Indicators:**
 
@@ -120,7 +111,7 @@ flowchart TD
 - Go: go.mod, go.sum
 - Rust: Cargo.toml
 
-#### Desktop Platform Detection
+### Desktop Platform Detection
 
 **Indicators:**
 
@@ -138,9 +129,9 @@ flowchart TD
 - WPF/WinForms: .csproj, App.xaml
 - Qt: .pro, CMakeLists.txt
 
-### Step 2: Extract Platform Metadata
+---
 
-For each detected platform, extract:
+## Metadata Extraction Fields
 
 | Field | Source | Example |
 |-------|--------|---------|
@@ -152,93 +143,9 @@ For each detected platform, extract:
 | config_files | List of config file paths | ["package.json", "tsconfig.json"] |
 | convention_files | Lint/format config files | [".eslintrc.js", ".prettierrc"] |
 
-### Step 3: Generate techs-manifest.json
-
-1. **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` value
-
-2. **Create JSON file** with detected platforms:
-
-```json
-{
-  "generated_at": "{{timestamp_from_get_timestamp}}",
-  "source_path": "/project",
-  "language": "zh",
-  "platforms": [
-    {
-      "platform_id": "web-react",
-      "platform_type": "web",
-      "framework": "react",
-      "language": "typescript",
-      "source_path": "src/web",
-      "config_files": [
-        "src/web/package.json",
-        "src/web/tsconfig.json",
-        "src/web/vite.config.ts"
-      ],
-      "convention_files": [
-        "src/web/.eslintrc.js",
-        "src/web/.prettierrc"
-      ]
-    },
-    {
-      "platform_id": "backend-nestjs",
-      "platform_type": "backend",
-      "framework": "nestjs",
-      "language": "typescript",
-      "source_path": "src/server",
-      "config_files": [
-        "src/server/package.json",
-        "src/server/nest-cli.json",
-        "src/server/tsconfig.json"
-      ],
-      "convention_files": [
-        "src/server/.eslintrc.js"
-      ]
-    }
-  ]
-}
-```
-
-### Step 4: Report Results
-
-```
-Stage 1 completed: Technology Platform Detection
-- Platforms Detected: {{platform_count}}
-  - web-react: React 18.2.0, TypeScript 5.3.0
-  - backend-nestjs: NestJS 10.0.0, TypeScript 5.3.0
-- Configuration Files Found: {{config_file_count}}
-- Output: {{output_path}}/techs-manifest.json
-- Next: Dispatch parallel tasks for Stage 2 (Tech Document Generation)
-```
-
-## Reference Guides
-
-### Platform Detection Reference
-
-#### Multiple Platforms in Same Project
-
-If a project contains multiple platforms (e.g., web + backend + mobile):
-- Detect each platform separately
-- Assign unique platform_id for each
-- Include all platforms in manifest
-
-#### Monorepo Structure
-
-For monorepos with multiple packages:
-- Detect platforms in each package directory
-- Use relative paths for source_path
-- Example: `packages/web-app` → web-react platform
-
-#### Framework Version Detection
-
-Extract version information when available:
-- From package.json dependencies
-- From pom.xml version tags
-- Include in report but not in manifest (manifest focuses on structure)
-
-#### Platform Mapping to bizs-init
+---
+
+## Platform Mapping Consistency
 
 Ensure consistency with modules.json by using standardized platform identifiers from `platform-mapping.json`:
 
@@ -248,6 +155,7 @@ Ensure consistency with modules.json by using standardized platform identifiers
 - `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 |
@@ -267,3 +175,14 @@ Ensure consistency with modules.json by using standardized platform identifiers
 - [ ] 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.

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

@@ -1,49 +1,3 @@
----
-name: speccrew-knowledge-techs-init-xml
-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
----
-
-# 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
-
-- "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
-
-## Workflow
-
-> **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-init-main" status="pending" version="1.0" desc="Technology platform detection and manifest generation">
 
@@ -258,146 +212,3 @@ Stage 1 completed: Technology Platform Detection
   </block>
 
 </workflow>
-```
-
----
-
-## 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.