speccrew 0.6.69 → 0.7.1

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

@@ -0,0 +1,173 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="requirement-assess-main" status="pending" version="1.0" desc="Quick impact assessment for new requirements">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="requirement_text" required="true" type="string" desc="New requirement description"/>
+    <field name="workspace_path" required="true" type="string" desc="Absolute path to speccrew workspace"/>
+    <field name="system_overview_path" required="false" type="string" desc="Path to system-overview.md"/>
+    <field name="language" required="true" type="string" desc="Target language for output"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="mandatory" desc="Execution constraints">
+    <field name="text">This skill is READ-ONLY - do not modify any files</field>
+    <field name="text">Use knowledge graph query for cross-module dependency analysis</field>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="Requirement Assessment" status="pending" desc="Assess new requirement impact">
+
+    <!-- Step 1: Understand the Requirement -->
+    <block type="task" id="B1" action="analyze" desc="Analyze the new requirement">
+      <field name="input" value="${requirement_text}"/>
+      <field name="extract">
+        - What business problem does it solve?
+        - What entities are involved?
+        - What processes are affected?
+      </field>
+      <field name="output" var="requirement_analysis"/>
+    </block>
+
+    <!-- Step 2: Load System Context -->
+    <block type="task" id="B2" action="read-file" desc="Read system overview">
+      <field name="path" value="${workspace_path}/knowledges/bizs/system-overview.md"/>
+      <field name="on_error">continue</field>
+      <field name="output" var="system_overview"/>
+    </block>
+
+    <!-- Step 3: Identify potentially affected modules -->
+    <block type="task" id="B3" action="analyze" desc="Identify potentially affected modules">
+      <field name="input">
+        requirement: ${requirement_analysis}
+        system_overview: ${system_overview}
+      </field>
+      <field name="identify">
+        - Which business domain the requirement belongs to
+        - Which modules are potentially related
+        - Which business processes are involved
+      </field>
+      <field name="output" var="affected_modules"/>
+    </block>
+
+    <!-- Step 4: Load related module overviews -->
+    <block type="loop" id="L1" over="${affected_modules}" as="module" desc="Load related module overviews">
+      <block type="task" id="B4" action="read-file" desc="Read module overview">
+        <field name="path" value="${workspace_path}/knowledges/bizs/${module.name}/${module.name}-overview.md"/>
+        <field name="on_error">continue</field>
+        <field name="output" var="module_overview"/>
+      </block>
+    </block>
+
+    <!-- Step 5: Query Knowledge Graph -->
+    <block type="task" id="B5" action="run-skill" desc="Query knowledge graph for dependencies">
+      <field name="skill">speccrew-knowledge-graph-query</field>
+      <field name="action">trace-dependencies</field>
+      <field name="entities" value="${affected_modules.entities}"/>
+      <field name="output" var="dependency_graph"/>
+    </block>
+
+    <!-- Step 6: Determine Change Type -->
+    <block type="task" id="B6" action="analyze" desc="Determine change type using decision tree">
+      <field name="input">
+        requirement: ${requirement_analysis}
+        affected_modules: ${affected_modules}
+        dependencies: ${dependency_graph}
+      </field>
+      <field name="decision_tree">
+        IF involves new business entity -> NEW FEATURE
+        ELSE IF modifies core attributes of existing entity -> MODIFICATION
+        ELSE IF adds new process steps but reuses existing entities -> MIXED
+        ELSE IF affects cross-module data flow -> CROSS-MODULE CHANGE
+        ELSE IF can be handled by configuration -> CONFIGURATION
+      </field>
+      <field name="output" var="change_type"/>
+    </block>
+
+    <!-- Step 7: Identify Impact Scope -->
+    <block type="task" id="B7" action="analyze" desc="Identify impact scope">
+      <field name="input">
+        affected_modules: ${affected_modules}
+        dependency_graph: ${dependency_graph}
+      </field>
+      <field name="identify">
+        - Direct modules: Modules explicitly mentioned in requirement
+        - Dependency modules: Upstream/downstream from graph query
+        - External integrations: Third-party systems
+        - Data entities: New or modified entities
+      </field>
+      <field name="output" var="impact_scope"/>
+    </block>
+
+    <!-- Step 8: Assess Risk Level -->
+    <block type="task" id="B8" action="analyze" desc="Assess risk level">
+      <field name="input">
+        impact_scope: ${impact_scope}
+        change_type: ${change_type}
+      </field>
+      <field name="risk_factors">
+        - Scope: Affects 3+ modules = High
+        - Data: Modifies core entity structure = High
+        - Integration: Changes external API contracts = High
+        - Process: Alters critical business flow = High
+        - State: Modifies entity state machine = High
+      </field>
+      <field name="output" var="risk_level"/>
+    </block>
+
+    <!-- Step 9: Recommend Workflow Path -->
+    <block type="task" id="B9" action="analyze" desc="Recommend workflow path">
+      <field name="input">
+        impact_scope: ${impact_scope}
+        change_type: ${change_type}
+        risk_level: ${risk_level}
+      </field>
+      <field name="recommendation_matrix">
+        - 1 module, low risk, clear domain -> Simple PRD (skip ISA-95 modeling)
+        - 2+ modules, medium risk -> Full requirement-analysis with ISA-95 modeling
+        - Cross-module, high risk -> Full requirement-analysis + Master-Sub PRD
+        - Configuration only -> Direct implementation, PRD optional
+      </field>
+      <field name="output" var="recommendation"/>
+    </block>
+
+    <!-- Step 10: Generate Assessment Report -->
+    <block type="task" id="B10" action="generate" desc="Generate assessment report">
+      <field name="template">Assessment Report Template</field>
+      <field name="fill_data">
+        requirement_summary: ${requirement_analysis}
+        change_type: ${change_type}
+        impact_scope: ${impact_scope}
+        risk_level: ${risk_level}
+        recommendation: ${recommendation}
+        graph_findings: ${dependency_graph}
+      </field>
+      <field name="output" var="assessment_report"/>
+    </block>
+
+    <!-- Checkpoint: Assessment complete -->
+    <block type="checkpoint" id="CP1" name="assessment-complete" desc="Verify assessment completed">
+      <field name="verify" value="${assessment_report} != null"/>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="change_type" from="${change_type}" type="string" desc="Change type: New Feature, Modification, Mixed, Cross-module, Configuration"/>
+    <field name="impact_scope" from="${impact_scope}" type="object" desc="Impact scope with direct and indirect modules"/>
+    <field name="risk_level" from="${risk_level}" type="string" desc="Risk level: Low, Medium, High"/>
+    <field name="recommendation" from="${recommendation}" type="string" desc="Recommended workflow path"/>
+    <field name="assessment_report" from="${assessment_report}" type="string" desc="Complete assessment report"/>
+    <field name="message" value="Requirement assessment completed" type="string" desc="Status message"/>
+  </block>
+
+</workflow>

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

@@ -34,232 +34,11 @@ Applies ISA-95 Stage 1 (Domain Description) for clarification:
 
 ---
 
-# 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: Load Requirement Document
-
-**Actions:**
-1. Read `requirement_file`
-2. Extract: business problem, target users, functional scope, constraints
-
-## Step 2: Load System Knowledge (IF EXISTS)
-
-**Actions:**
-1. Read `knowledges/bizs/system-overview.md` if exists
-2. Read related `{module}/{module}-overview.md` files if exist
-
-> ⚠️ Knowledge files are OPTIONAL. Proceed without them if absent.
-
-## Step 3: Determine Complexity Mode
-
-**Auto-detect criteria:**
-
-| Criteria | Simple | Complex |
-|----------|--------|---------|
-| Modules | 1 | 2+ or new domain |
-| Features | 1-5 | 6+ |
-| Integration points | 0-1 | 2+ |
-
-**Logic:** `complex` if modules >= 2 OR features >= 6 OR new_domain
-
-## Step 4: Execute Clarification (Dual Mode)
-
-### 4.1 Simple Mode
-
-- 1-3 key questions, chat-based
-- Topics: What to change, what the change is, business reason, acceptance criteria
-
-> ⚠️ **Switch to file-based if 4+ questions needed**
-
-### 4.2 Complex Mode (File-Based)
-
-> ⚠️ **All rounds use file-based interaction, NOT chat-based.**
-
-**Clarification Loop — Condition-Driven, No Round Limit**
-
-The clarification process continues until ALL sufficiency checks pass. There is NO fixed round limit.
-
-**Initial Round: Core Understanding**
-
-Create `.clarification-questions-round-1.md`:
-```markdown
-# Requirements Clarification - Round 1
-
-> Fill answers after each "**Answer:**" marker, then notify me.
-
-## 1. Business Background & Goals
-Based on the document, the system aims to solve: [points]
-
-**Questions:**
-- Is this understanding correct?
-- What is the primary business goal?
-
-**Answer:** <!-- Fill here -->
-
-## 2. Target Users & Scenarios
-Roles identified: [list]
-
-**Questions:**
-- Additional roles not mentioned?
-- Primary use cases for each role?
-
-**Answer:** <!-- Fill here -->
-
-## 3. System Scope & Boundaries
-Scope includes: [modules]
-
-**Questions:**
-- All modules required for Phase 1?
-- What is explicitly out of scope?
-
-**Answer:** <!-- Fill here -->
-```
-
-Notify user:
-```
-📝 Round 1 questions written to:
-`01.product-requirement/.clarification-questions-round-1.md`
-
-Please fill answers after each "**Answer:**" marker, save, and notify me.
-```
-
-**HARD STOP** — Wait for user confirmation, then read file.
-
-**Subsequent Rounds — Continue Until Sufficiency Checks Pass**
-
-After each round:
-1. Read the answered file
-2. Perform sufficiency check (see Step 5)
-3. If ALL 4 checks pass → Proceed to Step 6
-4. If ANY check fails → Generate next round with targeted follow-up questions
-
-Create `.clarification-questions-round-N.md` (N = current round number) with:
-- Follow-up questions based on gaps identified in sufficiency check
-- Focus on unanswered items, ambiguities, or new questions raised by user's answers
-- Maintain same file format with "**Answer:**" markers
-
-**Loop Termination Conditions:**
-- ALL 4 sufficiency checks pass, OR
-- User explicitly states no more questions needed
-
-> ⚠️ **Do NOT terminate early.** Continue clarification rounds until sufficiency is achieved.
-> The round counter (N) has NO upper limit.
-
-## Step 5: Sufficiency Check
-
-> ⚠️ **ALL 4 checks must pass before proceeding.**
-
-| # | Check Item | Pass Criteria |
-|---|------------|---------------|
-| 1 | Scope boundaries are clear | Explicit in/out scope defined |
-| 2 | Key business rules are documented | At least 1 rule identified |
-| 3 | Priority/phasing decisions are made | Phase 1 scope is clear |
-| 4 | Integration boundaries are identified | Integration points listed or "none" confirmed |
-
-**Logic:** If all 4 pass → Step 6. Else → continue to next clarification round.
-
-> ⚠️ **No round limit.** Continue generating clarification rounds until ALL checks pass.
-> Each round should focus on the specific gaps identified in the sufficiency check.
-
-## Step 6: Generate .clarification-summary.md
-
-**Output:** `{iteration_path}/01.product-requirement/.clarification-summary.md`
-
-**Format:**
-```markdown
-# Clarification Summary
-
-## Complexity
-- Level: [simple | complex]
-- Rationale: [reason]
-
-## Key Decisions
-| # | Decision | Rationale | Source |
-|---|----------|-----------|--------|
-| 1 | [text] | [reason] | Round X |
-
-## Clarification Q&A
-
-<!-- List all rounds that were conducted. Round count is dynamic. -->
-
-### Round 1
-| # | Question | Answer | Impact |
-|---|----------|--------|--------|
-| 1 | [Q] | [A] | [Impact] |
-
-### Round 2
-[Same format, if conducted]
-
-<!-- Add more rounds as needed until sufficiency checks pass -->
-
-## Sufficiency Checks
-- [x] Scope boundaries are clear
-- [x] Key business rules are documented
-- [x] Priority/phasing decisions are made
-- [x] Integration boundaries are identified
-
-## Notes
-[Additional remarks or gaps]
-```
-
-## Step 7: Initialize .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_clarification \
-  --passed true
-```
-
-**Generated structure:**
-```json
-{
-  "stage": "01_prd",
-  "checkpoints": {
-    "requirement_clarification": {
-      "passed": true,
-      "confirmed_at": "2026-04-10T12:00:00.000Z",
-      "description": "Requirement clarification completed",
-      "clarification_file": ".clarification-summary.md",
-      "complexity": "simple|complex",
-      "sufficiency_checks": {
-        "scope_boundaries": true,
-        "business_rules": true,
-        "priority_phasing": true,
-        "integration_boundaries": true
-      }
-    }
-  }
-}
-```
-
-## Step 8: Output Completion
-
-```
-✅ Requirement Clarification Complete
-
-Complexity Level: [simple | complex]
-Clarification File: {path}/.clarification-summary.md
-Checkpoint File: {path}/.checkpoints.json
-
-Key Decisions:
-- [Decision 1]
-- [Decision 2]
-
-Sufficiency Checks: 4/4 ✅
-
-Next: Return to PM Agent for user confirmation before 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-clarify/workflow.agentflow.xml

@@ -0,0 +1,159 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<workflow id="requirement-clarify-main" status="pending" version="1.0" desc="Requirement clarification with dual-mode support">
+
+  <!-- ============================================================
+       Input Parameters Definition
+       ============================================================ -->
+  <block type="input" id="I1" desc="Workflow input parameters">
+    <field name="requirement_file" required="true" type="string" desc="Path to requirement document"/>
+    <field name="iteration_path" required="true" type="string" desc="Path to iteration directory"/>
+    <field name="complexity_hint" required="false" type="string" desc="simple or complex. Auto-detect if not provided"/>
+    <field name="language" required="true" type="string" desc="Language code for output content"/>
+  </block>
+
+  <!-- ============================================================
+       Global Constraints
+       ============================================================ -->
+  <block type="rule" id="R1" level="mandatory" desc="Execution constraints">
+    <field name="text">Always perform at least 1 clarification round</field>
+    <field name="text">Use file-based for complex mode or 4+ questions</field>
+    <field name="text">MUST pass all 4 Sufficiency Checks</field>
+  </block>
+
+  <block type="rule" id="R2" level="forbidden" desc="Forbidden actions">
+    <field name="text">Skip clarification based on urgency</field>
+    <field name="text">Use chat for complex requirements</field>
+    <field name="text">Manually write JSON files - MUST use update-progress.js</field>
+    <field name="text">Auto-proceed to Phase 4 without PM Agent's user confirmation gate</field>
+  </block>
+
+  <!-- ============================================================
+       Main Processing Sequence
+       ============================================================ -->
+  <sequence id="S1" name="Requirement Clarification" status="pending" desc="Clarify requirements with user">
+
+    <!-- Step 1: Load Requirement Document -->
+    <block type="task" id="B1" action="read-file" desc="Read requirement document">
+      <field name="path" value="${requirement_file}"/>
+      <field name="output" var="requirement_content"/>
+    </block>
+
+    <!-- Step 2: Load System Knowledge (IF EXISTS) -->
+    <block type="task" id="B2" action="read-file" desc="Read system overview if exists">
+      <field name="path" value="${workspace_path}/knowledges/bizs/system-overview.md"/>
+      <field name="on_error">continue</field>
+      <field name="output" var="system_overview"/>
+    </block>
+
+    <!-- Step 3: Determine Complexity Mode -->
+    <block type="gateway" id="G1" mode="exclusive" desc="Determine complexity mode">
+      <branch test="${complexity_hint} == 'simple'" name="Simple Mode">
+        <block type="task" id="B3" action="analyze" desc="Set simple mode">
+          <field name="set_var" name="complexity" value="simple"/>
+        </block>
+      </branch>
+      <branch test="${complexity_hint} == 'complex'" name="Complex Mode">
+        <block type="task" id="B4" action="analyze" desc="Set complex mode">
+          <field name="set_var" name="complexity" value="complex"/>
+        </block>
+      </branch>
+      <branch name="Auto-detect" default="true">
+        <block type="task" id="B5" action="analyze" desc="Auto-detect complexity">
+          <field name="input" value="${requirement_content}"/>
+          <field name="criteria">
+            - Simple: modules = 1, features = 1-5, integration = 0-1
+            - Complex: modules >= 2 OR features >= 6 OR new_domain
+          </field>
+          <field name="output" var="complexity"/>
+        </block>
+      </branch>
+    </block>
+
+    <!-- Step 4: Execute Clarification -->
+    <block type="gateway" id="G2" mode="exclusive" desc="Execute clarification based on mode">
+      <branch test="${complexity} == 'simple'" name="Simple Mode Clarification">
+        <block type="task" id="B6" action="analyze" desc="Simple mode: 1-3 key questions">
+          <field name="topics">
+            - What to change
+            - What the change is
+            - Business reason
+            - Acceptance criteria
+          </field>
+          <field name="output" var="clarification_qa"/>
+        </block>
+      </branch>
+      <branch test="${complexity} == 'complex'" name="Complex Mode Clarification">
+        <!-- Clarification Loop -->
+        <block type="loop" id="L1" condition="sufficiency_checks_passed == false" desc="Clarification rounds until sufficiency">
+          <block type="task" id="B7" action="generate" desc="Create clarification questions file">
+            <field name="output_path" value="${iteration_path}/01.product-requirement/.clarification-questions-round-{round}.md"/>
+            <field name="sections">
+              - Business Background & Goals
+              - Target Users & Scenarios
+              - System Scope & Boundaries
+            </field>
+            <field name="output" var="questions_file"/>
+          </block>
+
+          <block type="event" id="E1" action="confirm" title="Clarification Round {round}" type="wait" desc="Wait for user to answer questions">
+            <field name="message">Round {round} questions written. Please fill answers and notify me.</field>
+          </block>
+
+          <block type="task" id="B8" action="read-file" desc="Read answered questions">
+            <field name="path" value="${questions_file}"/>
+            <field name="output" var="answered_questions"/>
+          </block>
+
+          <!-- Sufficiency Check -->
+          <block type="task" id="B9" action="analyze" desc="Perform sufficiency check">
+            <field name="checks">
+              1. Scope boundaries are clear - Explicit in/out scope defined
+              2. Key business rules are documented - At least 1 rule identified
+              3. Priority/phasing decisions are made - Phase 1 scope is clear
+              4. Integration boundaries are identified - Integration points listed or "none" confirmed
+            </field>
+            <field name="output" var="sufficiency_result"/>
+          </block>
+        </block>
+      </branch>
+    </block>
+
+    <!-- Step 5: Generate .clarification-summary.md -->
+    <block type="task" id="B10" action="generate" desc="Generate clarification summary">
+      <field name="output_path" value="${iteration_path}/01.product-requirement/.clarification-summary.md"/>
+      <field name="sections">
+        - Complexity level and rationale
+        - Key decisions table
+        - Clarification Q&A (all rounds)
+        - Sufficiency checks results
+        - Notes
+      </field>
+      <field name="output" var="summary_path"/>
+    </block>
+
+    <!-- Step 6: Initialize .checkpoints.json -->
+    <block type="task" id="B11" action="run-script" desc="Initialize 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_clarification --passed true</field>
+      <field name="output" var="checkpoint_result"/>
+    </block>
+
+    <!-- Checkpoint: Clarification complete -->
+    <block type="checkpoint" id="CP1" name="clarification-complete" desc="Verify clarification completed">
+      <field name="file" value="${summary_path}"/>
+      <field name="verify" value="file_exists(${summary_path})"/>
+    </block>
+
+  </sequence>
+
+  <!-- ============================================================
+       Output Results
+       ============================================================ -->
+  <block type="output" id="O1" desc="Workflow output results">
+    <field name="clarification_file" from="${summary_path}" type="string" desc="Path to clarification summary"/>
+    <field name="checkpoint_file" value="${iteration_path}/01.product-requirement/.checkpoints.json" type="string" desc="Path to checkpoints file"/>
+    <field name="complexity" from="${complexity}" type="string" desc="Complexity level: simple or complex"/>
+    <field name="sufficiency_checks" value="4/4 passed" type="string" desc="Sufficiency check results"/>
+    <field name="message" value="Requirement clarification completed" type="string" desc="Status message"/>
+  </block>
+
+</workflow>