speccrew 0.6.68 → 0.7.0

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

@@ -37,283 +37,11 @@ Applies ISA-95 Stages 1-3 as structured analysis framework:
 
 ---
 
-# Workflow
+# AgentFlow Definition
 
-## Absolute Constraints
+<!-- @agentflow: workflow.agentflow.xml -->
 
-> **Violation = task failure**
-
-1. **FORBIDDEN:** `create_file` for documents — use `search_replace` on templates
-2. **FORBIDDEN:** Full-file rewrite — use targeted `search_replace`
-3. **MANDATORY:** Template-first workflow
-
-## Step 1: Verify Prerequisites
-
-**MANDATORY:** `.clarification-summary.md` MUST exist in the iteration directory.
-
-**IF missing → ABORT immediately:**
-```
-❌ ERROR: .clarification-summary.md not found.
-   Path: {iteration_path}/01.product-requirement/.clarification-summary.md
-   
-   This skill requires completed clarification. Please run speccrew-pm-requirement-clarify first.
-```
-
-**Actions:**
-1. Read `.clarification-summary.md`
-2. Extract: complexity level, key decisions, clarified scope, business rules
-3. IF complexity == "simple" → Skip to Step 4 (minimal module design)
-
-## Step 2: ISA-95 Business Modeling (Complex Requirements)
-
-> ⚠️ **This is a THINKING PROCESS with user checkpoints.**
-
-### 2.1 Stage 1 - Domain Description
-
-**Actions:**
-- Define domain boundary (in-scope, out-of-scope)
-- Identify external participants (users, systems, agents)
-- Create domain glossary (business terms only)
-
-**Output format:**
-```markdown
-### Domain Description
-- **System Boundary**: [what's included/excluded]
-- **Actors**: [user roles, external systems]
-- **Domain Glossary**:
-  | Term | Definition |
-  |------|-----------|
-  | [term] | [definition] |
-```
-
-**Checkpoint A:** Present to user for confirmation.
-```
-📝 Domain Description Complete
-
-System Boundary: [summary]
-Actors: [list]
-
-Does this match your understanding? Reply "确认" to proceed or provide corrections.
-```
-
-**HARD STOP** — Wait for user confirmation before proceeding.
-
-### 2.2 Stage 2 - Functions in Domain (WBS)
-
-**Actions:**
-- Create WBS decomposition (2-3 levels)
-- Map functions to business capabilities
-- Identify module boundaries
-
-**Output format:**
-```markdown
-### Domain Functions (WBS)
-- Function 1
-  - Sub-function 1.1
-  - Sub-function 1.2
-- Function 2
-  - Sub-function 2.1
-```
-
-### 2.3 Stage 3 - Functions of Interest (MoSCoW)
-
-**Actions:**
-- Apply MoSCoW prioritization
-- Identify core vs non-core functions
-- Define MVP scope
-
-**Output format:**
-```markdown
-### Focus Functions (MoSCoW)
-| Priority | Function | Rationale |
-|----------|----------|-----------|
-| Must | [function] | [why core] |
-| Should | [function] | [why important] |
-| Could | [function] | [why deferred] |
-| Won't | [function] | [why excluded] |
-```
-
-**Checkpoint B:** Present MVP scope for confirmation.
-```
-📝 MVP Scope Defined
-
-Must-have (Phase 1): [list]
-Should-have (Phase 2): [list]
-
-Is this prioritization correct? Reply "确认" to proceed.
-```
-
-**HARD STOP** — Wait for user confirmation.
-
-**Checkpoint C:** Present complete analysis summary.
-```
-📝 ISA-95 Analysis Complete
-
-[Summary of all 3 stages]
-
-Ready to proceed with module decomposition? Reply "确认".
-```
-
-**HARD STOP** — Wait for final confirmation before Step 3.
-
-## Step 3: Module Decomposition & Ordering
-
-### 3.1 Define Module List
-
-**Actions:**
-- Map WBS functions to modules
-- Define scope for each module
-- Identify key entities per module
-
-**Output format:**
-```markdown
-## Module List (Total: {N} modules)
-| Module | Key | Scope | Key Entities | Owner Domain |
-|--------|-----|-------|-------------|--------------|
-| [Name] | [key] | [scope] | [entities] | [domain] |
-```
-
-> ⚠️ **MANDATORY:** Replace `{N}` with the actual module count. This count is used by downstream skills for structure validation.
-
-### 3.2 Cross-Module Dependency Matrix
-
-**Actions:**
-- Identify data flows between modules
-- Document dependency types (Data/API/Event)
-- Note shared entities
-
-**Output format:**
-```markdown
-## Dependency Matrix
-| Source Module | Target Module | Type | Description |
-|--------------|---------------|------|-------------|
-| [A] | [B] | Data | [shared entity] |
-```
-
-### 3.3 Implementation Phases
-
-**Actions:**
-- Sort modules by dependency (least dependent first)
-- Group into phases (typically 3)
-- Validate no circular dependencies
-
-**Output format:**
-```markdown
-## Implementation Phases
-- **Phase 1** (Foundation): [modules with no upstream deps]
-- **Phase 2** (Core): [modules depending on Phase 1]
-- **Phase 3** (Extension): [remaining modules]
-```
-
-**User Confirmation:**
-```
-📝 Module Decomposition Complete
-
-[Module list table]
-[Dependency matrix]
-[Implementation phases]
-
-Please review. Reply "确认" to finalize or request changes.
-```
-
-**HARD STOP** — Wait for user confirmation.
-
-## Step 4: Generate .module-design.md
-
-**Output:** `{iteration_path}/01.product-requirement/.module-design.md`
-
-**Complete format:**
-```markdown
-# Module Design
-
-## ISA-95 Analysis Summary
-
-### Domain Description
-- **System Boundary**: [description]
-- **Actors**: [list]
-- **Domain Glossary**:
-  | Term | Definition |
-  |------|-----------|
-  | [term] | [definition] |
-
-### Domain Functions (WBS)
-[WBS structure]
-
-### Focus Functions (MoSCoW)
-| Priority | Function | Rationale |
-|----------|----------|-----------|
-| Must | [fn] | [rationale] |
-| Should | [fn] | [rationale] |
-| Could | [fn] | [rationale] |
-
-## Module List (Total: {N} modules)
-| Module | Key | Scope | Key Entities | Owner Domain | Phase |
-|--------|-----|-------|-------------|--------------|-------|
-| [name] | [key] | [scope] | [entities] | [domain] | [1/2/3] |
-
-## Dependency Matrix
-| Source | Target | Type | Description |
-|--------|--------|------|-------------|
-| [A] | [B] | [type] | [desc] |
-
-## Implementation Phases
-- **Phase 1**: [foundation modules]
-- **Phase 2**: [dependent modules]
-- **Phase 3**: [independent modules]
-```
-
-**For simple requirements:** Include minimal sections (Domain Description + Module List with 1 module).
-
-## Step 5: Update .checkpoints.json
-
-> ⚠️ **MANDATORY: Use `update-progress.js` script for all JSON files.**
-
-```bash
-node speccrew-workspace/scripts/update-progress.js write-checkpoint \
-  --file {iteration_path}/01.product-requirement/.checkpoints.json \
-  --checkpoint requirement_modeling \
-  --passed true
-```
-
-**Generated structure:**
-```json
-{
-  "stage": "01_prd",
-  "checkpoints": {
-    "requirement_clarification": { ... },
-    "requirement_modeling": {
-      "passed": true,
-      "confirmed_at": "2026-04-10T12:00:00.000Z",
-      "description": "ISA-95 modeling and module decomposition completed",
-      "module_design_file": ".module-design.md",
-      "isa95_stages": {
-        "domain_description": true,
-        "functions_in_domain": true,
-        "functions_of_interest": true
-      },
-      "module_count": 3,
-      "implementation_phases": 3
-    }
-  }
-}
-```
-
-## Step 6: Output Completion
-
-```
-✅ Requirement Modeling Complete
-
-Module Design File: {path}/.module-design.md
-Checkpoint File: {path}/.checkpoints.json
-
-Summary:
-- Complexity: [simple | complex]
-- Modules: [count]
-- Phases: [count]
-- Dependencies: [count]
-
-Next: Proceed to PRD generation.
-```
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
 ---
 

package/.speccrew/skills/speccrew-pm-requirement-model/workflow.agentflow.xml

@@ -0,0 +1,210 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="requirement-model-main" status="pending" version="1.0" desc="ISA-95 business modeling and module decomposition">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="iteration_path" required="true" type="string" desc="Path to iteration directory"/>
+    <field name="clarification_file" required="false" type="string" desc="Path to clarification summary (default: {iteration_path}/01.product-requirement/.clarification-summary.md)"/>
+    <field name="language" required="true" type="string" desc="Language code for generated content"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="mandatory" desc="Execution constraints">
+    <field name="text">Verify .clarification-summary.md exists before starting</field>
+    <field name="text">Use 3 checkpoints (A/B/C) for progressive user confirmation</field>
+    <field name="text">Define clear module boundaries with minimal coupling</field>
+    <field name="text">Use update-progress.js for JSON files</field>
+  </block>
+
+  <block type="rule" id="R2" level="forbidden" desc="Forbidden actions">
+    <field name="text">Skip user checkpoints in complex mode</field>
+    <field name="text">Include technical implementation details</field>
+    <field name="text">Create circular module dependencies</field>
+    <field name="text">Manually write JSON files</field>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="Requirement Modeling" status="pending" desc="Apply ISA-95 Stages 1-3 for business modeling">
+
+    <!-- Step 1: Verify Prerequisites -->
+    <block type="task" id="B1" action="read-file" desc="Read clarification summary">
+      <field name="path" value="${clarification_file}"/>
+      <field name="output" var="clarification_content"/>
+    </block>
+
+    <!-- Gateway: Validate prerequisite -->
+    <block type="gateway" id="G1" mode="guard" desc="Verify clarification file exists"
+           test="${clarification_content} != null"
+           fail-action="stop">
+      <field name="message">ERROR: .clarification-summary.md not found. Run speccrew-pm-requirement-clarify first.</field>
+    </block>
+
+    <!-- Check complexity -->
+    <block type="gateway" id="G2" mode="exclusive" desc="Check complexity level">
+      <branch test="${clarification_content.complexity} == 'simple'" name="Simple - Skip to Step 4">
+        <block type="task" id="B2" action="analyze" desc="Set simple mode flag">
+          <field name="set_var" name="is_simple" value="true"/>
+        </block>
+      </branch>
+      <branch name="Complex - Full ISA-95" default="true">
+        <block type="task" id="B3" action="analyze" desc="Set complex mode flag">
+          <field name="set_var" name="is_simple" value="false"/>
+        </block>
+      </branch>
+    </block>
+
+    <!-- Step 2: ISA-95 Business Modeling (Complex Only) -->
+    <block type="gateway" id="G3" mode="exclusive" desc="Skip if simple mode">
+      <branch test="${is_simple} == false" name="Full ISA-95 Modeling">
+        <!-- 2.1 Stage 1 - Domain Description -->
+        <block type="task" id="B4" action="analyze" desc="Stage 1: Domain Description">
+          <field name="define">
+            - System Boundary: what's included/excluded
+            - Actors: user roles, external systems
+            - Domain Glossary: business terms only
+          </field>
+          <field name="output" var="domain_description"/>
+        </block>
+
+        <block type="event" id="E1" action="confirm" title="Checkpoint A" type="yesno" desc="Confirm domain description">
+          <field name="preview">Domain Description Complete. Does this match your understanding?</field>
+        </block>
+
+        <!-- 2.2 Stage 2 - Functions in Domain (WBS) -->
+        <block type="task" id="B5" action="analyze" desc="Stage 2: Functions in Domain (WBS)">
+          <field name="create">
+            - WBS decomposition (2-3 levels)
+            - Map functions to business capabilities
+            - Identify module boundaries
+          </field>
+          <field name="output" var="wbs_structure"/>
+        </block>
+
+        <!-- 2.3 Stage 3 - Functions of Interest (MoSCoW) -->
+        <block type="task" id="B6" action="analyze" desc="Stage 3: Functions of Interest (MoSCoW)">
+          <field name="apply">
+            - MoSCoW prioritization
+            - Identify core vs non-core functions
+            - Define MVP scope
+          </field>
+          <field name="output" var="moscow_priorities"/>
+        </block>
+
+        <block type="event" id="E2" action="confirm" title="Checkpoint B" type="yesno" desc="Confirm MVP scope">
+          <field name="preview">MVP Scope Defined. Is this prioritization correct?</field>
+        </block>
+
+        <block type="event" id="E3" action="confirm" title="Checkpoint C" type="yesno" desc="Confirm complete analysis">
+          <field name="preview">ISA-95 Analysis Complete. Ready to proceed with module decomposition?</field>
+        </block>
+      </branch>
+      <branch test="${is_simple} == true" name="Simple - Minimal Modeling">
+        <block type="event" id="E4" action="log" level="info" desc="Log simple mode">
+          <field name="message">Simple requirement - skipping full ISA-95 modeling</field>
+        </block>
+      </branch>
+    </block>
+
+    <!-- Step 3: Module Decomposition & Ordering -->
+    <block type="gateway" id="G4" mode="exclusive" desc="Module decomposition">
+      <branch test="${is_simple} == false" name="Complex - Full Decomposition">
+        <!-- 3.1 Define Module List -->
+        <block type="task" id="B7" action="analyze" desc="Define module list">
+          <field name="input" value="${wbs_structure}"/>
+          <field name="define">
+            - Map WBS functions to modules
+            - Define scope for each module
+            - Identify key entities per module
+          </field>
+          <field name="output" var="module_list"/>
+        </block>
+
+        <!-- 3.2 Cross-Module Dependency Matrix -->
+        <block type="task" id="B8" action="analyze" desc="Build dependency matrix">
+          <field name="identify">
+            - Data flows between modules
+            - Dependency types (Data/API/Event)
+            - Shared entities
+          </field>
+          <field name="output" var="dependency_matrix"/>
+        </block>
+
+        <!-- 3.3 Implementation Phases -->
+        <block type="task" id="B9" action="analyze" desc="Determine implementation phases">
+          <field name="sort">
+            - Sort modules by dependency (least dependent first)
+            - Group into phases (typically 3)
+            - Validate no circular dependencies
+          </field>
+          <field name="output" var="implementation_phases"/>
+        </block>
+
+        <block type="event" id="E5" action="confirm" title="Module Decomposition" type="yesno" desc="Confirm module decomposition">
+          <field name="preview">Module Decomposition Complete. Please review module list, dependency matrix, and implementation phases.</field>
+        </block>
+      </branch>
+      <branch test="${is_simple} == true" name="Simple - Single Module">
+        <block type="task" id="B10" action="analyze" desc="Create minimal module list">
+          <field name="create">
+            module_list: Single module from clarification
+            dependency_matrix: Empty
+            implementation_phases: Single phase
+          </field>
+          <field name="output" var="module_list"/>
+        </block>
+      </branch>
+    </block>
+
+    <!-- Step 4: Generate .module-design.md -->
+    <block type="task" id="B11" action="generate" desc="Generate module design document">
+      <field name="output_path" value="${iteration_path}/01.product-requirement/.module-design.md"/>
+      <field name="sections">
+        - ISA-95 Analysis Summary (if complex)
+        - Module List (Total: N modules)
+        - Dependency Matrix
+        - Implementation Phases
+      </field>
+      <field name="data">
+        domain_description: ${domain_description}
+        wbs_structure: ${wbs_structure}
+        moscow_priorities: ${moscow_priorities}
+        module_list: ${module_list}
+        dependency_matrix: ${dependency_matrix}
+        implementation_phases: ${implementation_phases}
+      </field>
+      <field name="output" var="module_design_path"/>
+    </block>
+
+    <!-- Step 5: Update .checkpoints.json -->
+    <block type="task" id="B12" action="run-script" desc="Update checkpoints via script">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" write-checkpoint --file "${iteration_path}/01.product-requirement/.checkpoints.json" --checkpoint requirement_modeling --passed true</field>
+      <field name="output" var="checkpoint_result"/>
+    </block>
+
+    <!-- Checkpoint: Modeling complete -->
+    <block type="checkpoint" id="CP1" name="modeling-complete" desc="Verify modeling completed">
+      <field name="file" value="${module_design_path}"/>
+      <field name="verify" value="file_exists(${module_design_path})"/>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="module_design_file" from="${module_design_path}" type="string" desc="Path to module design file"/>
+    <field name="checkpoint_file" value="${iteration_path}/01.product-requirement/.checkpoints.json" type="string" desc="Path to checkpoints file"/>
+    <field name="complexity" from="${clarification_content.complexity}" type="string" desc="Complexity level"/>
+    <field name="module_count" from="${module_list.count}" type="number" desc="Number of modules"/>
+    <field name="phases" from="${implementation_phases.count}" type="number" desc="Number of implementation phases"/>
+    <field name="message" value="Requirement modeling completed" type="string" desc="Status message"/>
+  </block>
+
+</workflow>

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

@@ -52,84 +52,11 @@ This skill applies ISA-95 Stages 1-3 in lightweight mode:
 
 ---
 
-## Workflow
+## AgentFlow Definition
 
-### Step 1: Read Clarification Summary
+<!-- @agentflow: workflow.agentflow.xml -->
 
-**Actions:**
-1. Read `.clarification-summary.md` from `{iteration_path}/01.product-requirement/`
-2. Extract: complexity level, key decisions, clarification Q&A, sufficiency checks
-
-**Verify complexity:**
-- IF complexity = "complex" → STOP and redirect to `speccrew-pm-requirement-analysis`
-- IF complexity = "simple" → proceed
-
-> **ISA-95 Stage 1 Thinking** — Scope boundary already confirmed in clarification. Extract module boundary and impacted roles from summary.
-
-### Step 2: Read PRD Template
-
-**Locate and read the PRD template:**
-
-1. **Search** for the template using glob pattern:
-   ```
-   **/speccrew-pm-requirement-analysis/templates/PRD-TEMPLATE.md
-   ```
-   > Note: Simple requirement skill shares the PRD template with the complex requirement skill.
-
-2. **Read** the found template file.
-
-> ⚠️ **DO NOT search in bizs/, knowledges/, or project source directories.**
-> The template is ALWAYS located in the skill's own `templates/` subfolder.
-> If glob returns no results, check if speccrew was properly initialized (`speccrew init`).
-
-### Step 3: Generate Single PRD
-
-Create PRD at: `speccrew-workspace/iterations/{iteration}/01.product-requirement/{feature-name}-prd.md`
-
-> **ISA-95 Stage 2 Thinking** — List only directly affected functions. No full WBS needed.
-
-**Section filling guidance:**
-
-| PRD Section | Simple Requirement Approach |
-|---|---|
-| 1. Background & Goals | 2-3 sentences. What's changing and why. |
-| 1.2 Domain Boundary | In-scope: the specific change. Out-of-scope: everything else. |
-| 1.3/1.4 Glossary | Only if new business terms introduced. Skip if unnecessary. |
-| 2. User Stories | 1-3 user stories maximum. |
-| 3. Functional Requirements | Brief description of the change. |
-| 3.3 Feature List | Simple table, 1-5 rows. |
-| 3.4 Feature Breakdown | 1-5 features. All P0. |
-| 4. Non-Functional Requirements | Only if relevant. Skip if not applicable. |
-| 5. Acceptance Criteria | 3-5 concrete, testable criteria. |
-| 6. Boundary | Clear in/out scope. |
-| 7. Assumptions | Only if there are assumptions to document. |
-
-> ⚠️ **Content Boundary Reminder for each section:**
-> - Background & Goals → Business reason only, NO technical architecture
-> - User Stories → "As a [role] I want [business action]" — NOT implementation method
-> - Functional Requirements → WHAT changes, not HOW to implement
-> - Feature List/Breakdown → Feature description is business outcome, NOT technical solution
-> - Acceptance Criteria → Business acceptance (e.g., "User can see result"), NOT technical tests (e.g., "API returns 200")
-
-> **ISA-95 Stage 3 Thinking** — All identified features are Must-have (P0). No MoSCoW filtering needed.
-
-### Step 4: Return to PM Agent
-
-**Output:**
-```
-📄 PRD Generated: {feature-name}-prd.md
-
-Summary:
-- Scope: {brief scope from clarification summary}
-- Features: {count} features
-- Modules affected: {module names}
-- Complexity: simple
-
-Returning to PM Agent for review and confirmation.
-```
-
-> **DO NOT wait for user confirmation in this skill.**
-> Verification and confirmation are handled by PM Agent Phase 5.
+> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md`
 
 ---