speccrew 0.7.31 → 0.7.32

package/.speccrew/agents/speccrew-task-worker.md

@@ -57,6 +57,26 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
 - DO NOT wait for confirmation before writing output files
 - If skill execution fails, report failure with details — do not ask user what to do
 
+### OUTPUT EFFICIENCY
+
+When executing design or document generation skills:
+- Generate content directly into the output file
+- DO NOT display full document sections in conversation
+- Only output brief block execution announcements
+- This is especially critical in batch mode where multiple Workers run simultaneously
+
+**FORBIDDEN output in conversation during design tasks:**
+- ASCII wireframes / UI prototypes
+- Mermaid diagrams (these go in the file only)
+- API endpoint lists
+- Data model tables
+- Full section content
+
+**Allowed output:**
+- Block execution announcements: "[Block B1] Designing UI prototypes..."
+- Error messages
+- Final completion summary (1-2 lines)
+
 ## Workflow
 
 ### 1. Receive Task

package/.speccrew/skills/speccrew-fd-feature-design/SKILL.md

@@ -187,8 +187,35 @@ node speccrew-workspace/scripts/update-progress.js write-checkpoint \
 
 Log: "✅ Checkpoint A (function_decomposition) passed and recorded"
 
+### OUTPUT EFFICIENCY RULES
+
+> **MANDATORY: Direct-to-File Output**
+> 
+> When generating Feature Spec content:
+> - **DO NOT** display design content (wireframes, interaction flows, API specs, data models) in the conversation
+> - **DO NOT** output intermediate design results as chat messages
+> - **DO** think through the design internally, then write directly to the output file
+> - **DO** only report brief status messages: "[Block X] Designing frontend for Function N..." 
+> 
+> **Rationale**: In batch mode, multiple Workers run simultaneously. Displaying full design content in chat wastes context window and creates confusion.
+>
+> **Allowed output in conversation**:
+> - Block execution announcements (1 line each)
+> - Error messages
+> - Checkpoint confirmation requests (when not skipped)
+> - Final completion summary (1-2 lines)
+>
+> **FORBIDDEN output in conversation**:
+> - ASCII wireframes / UI prototypes
+> - Mermaid diagrams (these go in the file only)
+> - API endpoint lists
+> - Data model tables
+> - Full section content
+
 ## Step 1: Frontend Design
 
+> ⚠️ **OUTPUT REMINDER**: Design content goes directly into the output file. DO NOT display wireframes or UI elements in conversation.
+
 ### 1.0 Conditional Execution
 
 `feature_type = "Page+API"` → Execute design; `feature_type = "API-only"` → Skip; Not provided → Execute (backward compatibility)
@@ -296,6 +323,8 @@ Document: `User Action → Frontend Response → Backend API Call`
 
 ## Step 2: Backend Design
 
+> ⚠️ **OUTPUT REMINDER**: Backend API designs go directly into the output file. DO NOT display API lists or processing logic in conversation.
+
 > **CRITICAL CONSTRAINT**: Backend design in Feature Spec must remain at the BUSINESS API level:
 > - Describe API endpoints as business operations (e.g., "Create Shop" operation with business parameters)
 > - Describe business validation rules in plain language (e.g., "Shop name must be unique within tenant")
@@ -334,6 +363,8 @@ Document: `User Action → Frontend Response → Backend API Call`
 
 ## Step 3: Data Model & Business Rules
 
+> ⚠️ **OUTPUT REMINDER**: Data models and business rules go directly into the output file. DO NOT display tables or validation rules in conversation.
+
 ### 3.1 New Data Structures
 
 | Field | Type | Constraints | Description |

package/.speccrew/skills/speccrew-fd-feature-design/workflow.agentflow.xml

@@ -202,6 +202,14 @@ Does this function breakdown align with your understanding of the requirements?<
        ============================================================ -->
   <sequence id="S1" name="Feature Design" status="pending" desc="Generate Feature Spec from analysis results">
 
+    <!-- Output Efficiency Rule -->
+    <block type="rule" id="R-OUTPUT-EFFICIENCY" level="mandatory" desc="Direct-to-file output only">
+      <field name="text">DO NOT display design content in conversation</field>
+      <field name="text">Think internally, write directly to output file</field>
+      <field name="text">Only output brief status messages and block announcements</field>
+      <field name="text">FORBIDDEN: wireframes, API lists, data tables in chat</field>
+    </block>
+
     <!-- Step 1.0: Prepare analysis results for design -->
     <block type="task" id="B1_0" action="analyze" desc="Prepare analysis data for design phase">
       <field name="input" value="${analyzed_functions}">${prd_content}${feature_id}${feature_name}${feature_type}${frontend_platforms}</field>

package/package.json

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