speccrew 0.6.53 → 0.6.55

package/.speccrew/skills/speccrew-knowledge-bizs-api-analyze-xml/SKILL.md

@@ -385,6 +385,34 @@ Before executing the workflow, verify the following inputs:
     <field name="message" value="Step 5a Status: COMPLETED - Template copied to ${documentPath}, ready for section filling"/>
   </block>
   
+  <!-- ==================== STEP 5-DYNAMIC: DYNAMIC SECTION GENERATION ==================== -->
+  <!-- Dynamic Section Generation Rule -->
+  <block type="rule" id="R-DYNAMIC-SECTIONS" level="mandatory" desc="Dynamic section generation rule">
+    <field name="text">BEFORE filling template sections, you MUST first count identified items (endpoints, components, etc.) and dynamically create the corresponding number of sections in the document.</field>
+    <field name="text">Step 1: Copy template skeleton to target path</field>
+    <field name="text">Step 2: For each identified endpoint/component, insert a new numbered sub-section (e.g., 2.1, 2.2, 2.3...) into the document</field>
+    <field name="text">Step 3: Fill each sub-section with the specific endpoint/component details</field>
+    <field name="text">NEVER rely on fixed template sections alone — the number of sections MUST match the number of identified items</field>
+  </block>
+  
+  <!-- Dynamically Generate Endpoint Sections -->
+  <block type="loop" id="L-ENDPOINT-SECTIONS" over="${endpoints}" as="endpoint" desc="Dynamically generate a section for each API endpoint">
+    <block type="task" id="B-EP-SECTION" action="generate" desc="Insert endpoint sub-section into document">
+      <field name="target" value="${documentPath}"/>
+      <field name="content">For endpoint ${endpoint.method} ${endpoint.path}: insert a ## 2.X sub-section containing Endpoint Information table, Request Parameters, Response Data, Business Flow, and Error Codes</field>
+      <field name="output" var="section_${endpoint.index}"/>
+    </block>
+  </block>
+  
+  <!-- Verify Section Count Matches Endpoint Count -->
+  <block type="checkpoint" id="CP-SECTIONS-COUNT" desc="Verify section count matches endpoint count">
+    <field name="verify" value="Number of generated 2.X sections == ${endpoints.length}"/>
+  </block>
+  
+  <block type="event" id="E-DYNAMIC" action="log" level="info" desc="Log dynamic sections status">
+    <field name="message" value="Step 5-Dynamic Status: COMPLETED - Generated ${endpoints.length} endpoint sections dynamically"/>
+  </block>
+  
   <!-- ==================== STEP 5B: FILL EACH SECTION USING SEARCH_REPLACE ==================== -->
   <!-- Calculate Dynamic Path Prefix -->
   <block type="task" id="B17" action="calculate-path-prefix" desc="Calculate path prefix">

package/.speccrew/skills/speccrew-knowledge-bizs-dispatch-xml/SKILL.md

@@ -132,7 +132,7 @@ Stage 4: System Summary
     <field name="max_concurrent_workers" required="false" type="number" default="5" desc="Maximum parallel Worker count"/>
     <field name="workspace_path" required="true" type="string" desc="Absolute path to speccrew-workspace directory"/>
     <field name="sync_state_bizs_dir" required="true" type="string" desc="Absolute path to knowledges/base/sync-state/knowledge-bizs/"/>
-    <field name="ide_skills_dir" required="true" type="string" desc="Absolute path to IDE skills directory (e.g., .qoder/skills, .cursor/skills)"/>
+    <field name="speccrew_skills_dir" required="true" type="string" desc="Absolute path to .speccrew/skills/ directory containing skill scripts"/>
     <field name="configs_dir" required="true" type="string" desc="Absolute path to docs/configs/ directory"/>
     <field name="graph_root" required="false" type="string" desc="Graph data output root path (absolute path preferred)" default="${workspace_path}/knowledges/bizs/graph"/>
     <field name="completed_dir" required="true" type="string" desc="Marker file output directory for Worker results (absolute path required)"/>
@@ -263,6 +263,10 @@ Continue with knowledge base generation?
       <field name="verify" value="${platforms.length} > 0"/>
     </block>
 
+    <block type="task" id="S0-B5" action="run-script" status="pending" desc="Update Stage 0 progress to completed">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage0 --status completed --output "Detected ${platforms.length} platforms"</field>
+    </block>
+
     <block type="event" id="S0-E4" action="log" level="info" desc="Report detected platform list">
     <field name="message">Detected ${platforms.length} platforms: ${platforms.names}</field>
     </block>
@@ -301,6 +305,10 @@ Continue with knowledge base generation?
       <field name="file" value="${sync_state_bizs_dir}/.progress.json"/>
       <field name="verify" value="true"/>
     </block>
+
+    <block type="task" id="S1a-B2" action="run-script" status="pending" desc="Update Stage 1a progress to completed">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage1a --status completed --output "Entry directories recognized for all platforms"</field>
+    </block>
   </sequence>
 
   <!-- ============================================================
@@ -316,7 +324,7 @@ Continue with knowledge base generation?
     <block type="loop" id="S1b-L1" over="${platforms}" as="platform" desc="Generate Feature inventory for each platform">
       <!-- Step 1: Read platform mapping config -->
       <block type="task" id="S1b-B1" action="run-script" status="pending" desc="Read platform mapping config">
-        <field name="command">node "${ide_skills_dir}/speccrew-knowledge-bizs-init-features/scripts/generate-inventory.js"</field>
+        <field name="command">node "${speccrew_skills_dir}/speccrew-knowledge-bizs-init-features/scripts/generate-inventory.js"</field>
         <field name="arg">--entryDirsFile</field>
         <field name="arg">${sync_state_bizs_dir}/entry-dirs-${platform.platformId}.json</field>
         <field name="output" var="features_${platform.platformId}"/>
@@ -333,6 +341,10 @@ Continue with knowledge base generation?
       <field name="verify" value="${all_features.length} > 0"/>
     </block>
 
+    <block type="task" id="S1b-B2" action="run-script" status="pending" desc="Update Stage 1b progress to completed">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage1b --status completed --output "${feature_count} features across ${platform_count} platforms"</field>
+    </block>
+
     <block type="event" id="S1b-E1" action="log" level="info" desc="Report Feature inventory statistics">
     <field name="message">Feature inventory initialized. ${feature_count} features across ${platform_count} platforms.</field>
     </block>
@@ -352,7 +364,7 @@ Continue with knowledge base generation?
       <branch test="${sync_mode} == 'incremental'" name="Incremental mode">
         <!-- Step 1: Execute Feature merge -->
         <block type="task" id="S1c-B1" action="run-script" status="pending" desc="Merge new and existing Feature inventories">
-          <field name="command">node "${ide_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/merge-features.js"</field>
+          <field name="command">node "${speccrew_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/merge-features.js"</field>
           <field name="arg">--syncStatePath</field>
           <field name="arg">${sync_state_bizs_dir}</field>
           <field name="arg">--completedDir</field>
@@ -373,7 +385,7 @@ Continue with knowledge base generation?
 
         <!-- Step 3: Mark stale Features -->
         <block type="task" id="S1c-B2" action="run-script" status="pending" desc="Clean up documents and markers for deleted Features">
-          <field name="command">node "${ide_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/mark-stale.js"</field>
+          <field name="command">node "${speccrew_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/mark-stale.js"</field>
           <field name="arg">--syncStatePath</field>
           <field name="arg">${sync_state_bizs_dir}</field>
           <field name="arg">--completedDir</field>
@@ -391,13 +403,21 @@ Continue with knowledge base generation?
       <field name="file" value="${sync_state_bizs_dir}/.progress.json"/>
       <field name="passed" value="true"/>
     </block>
+
+    <block type="task" id="S1c-B3" action="run-script" status="pending" desc="Update Stage 1c progress to completed">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage1c --status completed</field>
+    </block>
   </sequence>
 
   <!-- ============================================================
        Stage 2: Feature Analysis (Batch Processing)
        ============================================================ -->
   <sequence id="S2" name="Stage 2: Feature Analysis" status="pending" desc="Batch process Feature analysis, dispatch Workers to execute">
-    
+
+    <block type="task" id="S2-B-Start" action="run-script" status="pending" desc="Update Stage 2 progress to in_progress">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage2 --status in_progress</field>
+    </block>
+
     <block type="rule" id="S2-R1" level="mandatory" desc="Stage 2 mandatory rules">
       <field name="text">MUST use batch-orchestrator for batch management — DO NOT manually track batches</field>
       <field name="text">MUST dispatch Workers for feature analysis — DO NOT analyze features yourself</field>
@@ -426,7 +446,7 @@ Continue with knowledge base generation?
       
       <!-- Step 1: Get next batch -->
       <block type="task" id="S2-B1" action="run-script" status="pending" desc="Get next batch of pending Features">
-        <field name="command">node "${ide_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/batch-orchestrator.js" get-batch</field>
+        <field name="command">node "${speccrew_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/batch-orchestrator.js" get-batch</field>
         <field name="arg">--syncStatePath</field>
         <field name="arg">${sync_state_bizs_dir}</field>
         <field name="arg">--batchSize</field>
@@ -598,7 +618,7 @@ Requirements:
 
           <!-- Step 3: Process batch results -->
           <block type="task" id="S2-B3" action="run-script" status="pending" desc="Collect and process batch Worker results">
-            <field name="command">node "${ide_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/batch-orchestrator.js" process-results</field>
+            <field name="command">node "${speccrew_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/batch-orchestrator.js" process-results</field>
             <field name="arg">--syncStatePath</field>
             <field name="arg">${sync_state_bizs_dir}</field>
             <field name="arg">--graphRoot</field>
@@ -620,6 +640,10 @@ Requirements:
       <field name="verify" value="${pending_features.length} == 0"/>
     </block>
 
+    <block type="task" id="S2-B-End" action="run-script" status="pending" desc="Update Stage 2 progress to completed">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage2 --status completed --output "${analyzed_count} features analyzed"</field>
+    </block>
+
     <block type="event" id="S2-E-Final" action="log" level="info" desc="Stage 2 complete">
     <field name="message">Stage 2 Milestone: Feature analysis complete. ${analyzed_count} features analyzed, ${failed_count} failed. ${graph_count} graph data files generated.</field>
     </block>
@@ -684,6 +708,10 @@ Requirements:
       <field name="passed" value="true"/>
     </block>
 
+    <block type="task" id="S3-B5" action="run-script" status="pending" desc="Update Stage 3 progress to completed">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage3 --status completed --output "${module_count} modules summarized"</field>
+    </block>
+
     <block type="event" id="S3-E1" action="log" level="info" desc="Stage 3 complete">
     <field name="message">Stage 3 Milestone: Module summaries complete. ${module_count} modules summarized.</field>
     </block>
@@ -739,6 +767,10 @@ Requirements:
     <block type="event" id="S35-E2" action="log" level="info" desc="Stage 3.5 complete">
     <field name="message">Stage 3.5 Milestone: UI style patterns extracted. ${pattern_count} patterns extracted from ${frontend_platform_count} platforms.</field>
     </block>
+
+    <block type="task" id="S35-B2" action="run-script" status="pending" desc="Update Stage 3.5 progress to completed">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage3.5 --status completed --output "${pattern_count} patterns extracted"</field>
+    </block>
   </sequence>
 
   <!-- ============================================================
@@ -786,6 +818,10 @@ Requirements:
       <field name="passed" value="true"/>
     </block>
 
+    <block type="task" id="S4-B3" action="run-script" status="pending" desc="Update Stage 4 progress to completed">
+      <field name="command">node "${workspace_path}/scripts/update-progress.js" update-workflow --file "${sync_state_bizs_dir}/WORKFLOW-PROGRESS.json" --stage Stage4 --status completed --output "System overview generated"</field>
+    </block>
+
     <block type="event" id="S4-E1" action="log" level="info" desc="Stage 4 complete">
     <field name="message">Stage 4 Milestone: System overview generated. All stages complete. Pipeline finished successfully.</field>
     </block>
@@ -803,7 +839,7 @@ Requirements:
       <field name="message">Worker ${error.worker} failed: ${error.message}</field>
       </block>
       <block type="task" id="EH1-B1" action="run-script" desc="Update failed status">
-        <field name="command">node "${ide_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/update-feature-status.js"</field>
+        <field name="command">node "${speccrew_skills_dir}/speccrew-knowledge-bizs-dispatch/scripts/update-feature-status.js"</field>
         <field name="arg">--featureId</field>
         <field name="arg">${error.feature_id}</field>
         <field name="arg">--status</field>

package/.speccrew/skills/speccrew-knowledge-bizs-ui-analyze-xml/SKILL.md

@@ -72,7 +72,7 @@ Analyze one specific UI feature from source code, extract business functionality
 }
 ```
 
-> **Note**: Graph data construction (nodes, edges, marker files) is handled by `speccrew-knowledge-bizs-ui-graph` Skill. This Skill only generates feature documentation.
+> **Note**: Graph data (.graph.json) is handled by `speccrew-knowledge-bizs-ui-graph` Skill. This Skill generates feature documentation AND writes `.done.json` completion marker.
 
 ## Workflow
 
@@ -306,7 +306,31 @@ Analyze one specific UI feature from source code, extract business functionality
       <field name="message">Step 5a Status: COMPLETED - Template copied to ${documentPath}</field>
     </block>
   </sequence>
-
+  
+  <!-- ==================== STEP 5-MID: DYNAMIC SECTION GENERATION ==================== -->
+  <!-- Rule: Dynamic section generation before filling fixed sections -->
+  <block type="rule" id="R-DYNAMIC-SECTIONS" level="mandatory" desc="Dynamic section generation rule">
+    <field name="text">BEFORE filling template sections, you MUST first count identified UI components and dynamically create the corresponding number of sections in the document.</field>
+    <field name="text">Step 1: Copy template skeleton to target path</field>
+    <field name="text">Step 2: For each identified UI component/area, insert a new numbered sub-section (e.g., 2.1, 2.2, 2.3...) into the document</field>
+    <field name="text">Step 3: Fill each sub-section with the specific component details (wireframe, interactions, events)</field>
+    <field name="text">NEVER rely on fixed template sections alone — the number of sections MUST match the number of identified UI components</field>
+  </block>
+  
+  <!-- Loop: Dynamically generate a section for each UI component -->
+  <block type="loop" id="L-COMPONENT-SECTIONS" over="${analysisResult.components}" as="component" desc="Dynamically generate a section for each UI component">
+    <block type="task" id="B-COMP-SECTION" action="generate" desc="Insert component sub-section into document">
+      <field name="target" value="${documentPath}"/>
+      <field name="content">For component ${component.name} (type: ${component.type}): insert a ## 2.X sub-section containing Component Wireframe, Props/Events table, Interaction Flow, and State Management</field>
+      <field name="output" var="section_${component.index}"/>
+    </block>
+  </block>
+  
+  <!-- Checkpoint: Verify section count matches component count -->
+  <block type="checkpoint" id="CP-SECTIONS-COUNT" desc="Verify section count matches component count">
+    <field name="verify">Number of generated 2.X sections == ${analysisResult.components.length}</field>
+  </block>
+  
   <!-- ==================== STEP 5B: FILL EACH SECTION USING SEARCH_REPLACE ==================== -->
   <sequence id="S5b" name="Step 5b: Fill Sections" status="pending" desc="Fill document sections">
     <!-- Section 1: Content Overview -->
@@ -380,6 +404,49 @@ Analyze one specific UI feature from source code, extract business functionality
     </block>
   </sequence>
 
+  <!-- ==================== STEP 7: WRITE COMPLETION MARKERS ==================== -->
+  <!-- Calculate Subpath from Source Path -->
+  <block type="task" id="B29" action="calculate-subpath" desc="Calculate subpath">
+    <field name="sourcePath" value="${sourcePath}"/>
+    <field name="output" var="subpath" from="calculation.subpath"/>
+  </block>
+  
+  <!-- Generate Marker File Name -->
+  <block type="task" id="B30" action="generate-marker-name" desc="Generate marker name">
+    <field name="module" value="${module}"/>
+    <field name="subpath" value="${subpath}"/>
+    <field name="fileName" value="${fileName}"/>
+    <field name="output" var="markerName" from="generation.name"/>
+  </block>
+  
+  <!-- Pre-write Verification -->
+  <block type="checkpoint" id="CP6" name="pre-write-check" desc="Pre-write verification">
+    <field name="verify" value="${fileName} does-not-contain '.' AND ${sourceFile} matches 'features-*.json'"/>
+  </block>
+  
+  <!-- Write .done.json File -->
+  <block type="task" id="B31" action="create-file" desc="Write done marker file">
+    <field name="target" value="${completed_dir}/${markerName}.done.json"/>
+    <field name="content" value="{
+  &quot;fileName&quot;: &quot;${fileName}&quot;,
+  &quot;sourcePath&quot;: &quot;${sourcePath}&quot;,
+  &quot;sourceFile&quot;: &quot;${sourceFile}&quot;,
+  &quot;module&quot;: &quot;${module}&quot;,
+  &quot;documentPath&quot;: &quot;${documentPath}&quot;,
+  &quot;status&quot;: &quot;${status}&quot;,
+  &quot;analysisNotes&quot;: &quot;${message}&quot;
+}"/>
+  </block>
+  
+  <!-- Verify Marker File Written -->
+  <block type="checkpoint" id="CP7" name="marker-written" desc="Marker file written">
+    <field name="verify" value="file.exists(${completed_dir}/${markerName}.done.json)"/>
+  </block>
+  
+  <block type="event" id="E10" action="log" level="info" desc="Log marker status">
+    <field name="message" value="Step 7 Status: COMPLETED - Done marker file written to ${completed_dir}/${markerName}.done.json"/>
+  </block>
+
   <!-- ==================== FINAL OUTPUT ==================== -->
   <block type="output" id="O1" desc="UI feature analysis output results">
     <field name="status" value="success"/>
@@ -449,8 +516,9 @@ When the task is complete, report the following:
 
 **Files Generated:**
 - `{{documentPath}}` - Feature documentation
+- `completed_dir/markerName.done.json` - Completion marker
 
-**Note:** Graph data construction (nodes, edges, marker files) is handled by `speccrew-knowledge-bizs-ui-graph` Skill.
+**Note:** Graph data (.graph.json) is handled by `speccrew-knowledge-bizs-ui-graph` Skill. The `.done.json` completion marker is written by this Skill in Step 7.
 
 ## Checklist
 
@@ -463,3 +531,4 @@ When the task is complete, report the following:
 - [ ] All sections filled using search_replace
 - [ ] All content in target language (`{{language}}`)
 - [ ] Results reported in JSON format
+- [ ] Done marker file written to completed_dir

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "speccrew",
-  "version": "0.6.53",
+  "version": "0.6.55",
   "description": "Spec-Driven Development toolkit for AI-powered IDEs",
   "author": "charlesmu99",
   "repository": {