speccrew 0.1.9 → 0.1.11

package/.speccrew/skills/speccrew-test-case-design/SKILL.md

@@ -12,6 +12,16 @@ tools: Read, Write, Glob, Grep
 
 # Workflow
 
+## Absolute Constraints
+
+> **These rules apply to ALL document generation steps. Violation = task failure.**
+
+1. **FORBIDDEN: `create_file` for documents** — NEVER use `create_file` to write the test case design document. It MUST be created by copying the template then filling sections with `search_replace`.
+
+2. **FORBIDDEN: Full-file rewrite** — NEVER replace the entire document content in a single operation. Always use targeted `search_replace` on specific sections.
+
+3. **MANDATORY: Template-first workflow** — Copy template MUST execute before filling sections. Skipping copy and writing content directly is FORBIDDEN.
+
 ## Step 1: Read Feature Spec
 
 Read the feature spec document specified by `feature_spec_path`:
@@ -243,21 +253,31 @@ Read the template file:
 speccrew-test-case-design/templates/TEST-CASE-DESIGN-TEMPLATE.md
 ```
 
-### 7.3 Fill Template
+### 7.3 Copy Template to Document Path
+
+1. **Read the template file**: `templates/TEST-CASE-DESIGN-TEMPLATE.md` (loaded in 7.2)
+2. **Replace top-level placeholders** (feature name, module, date, etc.)
+3. **Create the document** using `create_file` at the path from Step 7.1
+4. **Verify**: Document has complete section structure ready for filling
+
+### 7.4 Fill Each Section Using search_replace
 
-Fill in the template with:
+Fill each section with test case data using `search_replace`.
 
-| Section | Content |
-|---------|---------|
-| Test Overview | Feature name, module, scope, related documents |
-| Test Case Matrix | All test cases organized by category |
-| Test Data Definition | Normal, boundary, and exception data sets |
-| Coverage Traceability | Requirement-to-test-case mapping |
-| Notes | Additional information and assumptions |
+> ⚠️ **CRITICAL CONSTRAINTS:**
+> - **FORBIDDEN: `create_file` to rewrite the entire document**
+> - **MUST use `search_replace` to fill each section individually**
+> - **All section titles MUST be preserved**
 
-### 7.4 Write Document
+**Section Filling Order:**
 
-Write the completed test case design document to the output path.
+| Section | Content Source |
+|---------|---------------|
+| **Test Overview** | Feature name, module, scope, related documents |
+| **Test Case Matrix** | All test cases organized by category from Step 5 |
+| **Test Data Definition** | Normal, boundary, and exception data sets |
+| **Coverage Traceability** | Requirement-to-test-case mapping from Step 6 |
+| **Notes** | Additional information and assumptions |
 
 # Key Rules
 

package/.speccrew/skills/speccrew-test-code-gen/SKILL.md

@@ -12,6 +12,18 @@ tools: Read, Write, Glob, Grep
 
 # Workflow
 
+## Absolute Constraints
+
+> **These rules apply to document generation steps (Step 7). Violation = task failure.**
+
+1. **FORBIDDEN: `create_file` for plan document** — NEVER use `create_file` to write the test code plan document. It MUST be created by copying the template then filling sections with `search_replace`.
+
+2. **FORBIDDEN: Full-file rewrite** — NEVER replace the entire document content in a single operation. Always use targeted `search_replace` on specific sections.
+
+3. **MANDATORY: Template-first workflow** — Copy template MUST execute before filling sections.
+
+4. **CLARIFICATION: Test source code is NOT template-filled** — Actual test code files in Step 6 are written directly. The template-fill workflow applies ONLY to the Code Plan document in Step 7.
+
 ## Step 1: Read Test Cases
 
 Read the confirmed test case document specified by `test_cases_path`:
@@ -273,7 +285,32 @@ Generate files in dependency order:
 
 Output the code plan document for traceability:
 
-**Path**: `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/code/{platform_id}/[feature]-test-code-plan.md`
+### 7.1 Copy Template to Document Path
+
+1. **Read the template**: `templates/TEST-CODE-PLAN-TEMPLATE.md`
+2. **Replace top-level placeholders** (feature name, platform, date, etc.)
+3. **Create the document** using `create_file`:
+   - Target path: `speccrew-workspace/iterations/{number}-{type}-{name}/05.system-test/code/{platform_id}/[feature]-test-code-plan.md`
+   - Content: Template with top-level placeholders replaced
+4. **Verify**: Document has complete section structure
+
+### 7.2 Fill Each Section Using search_replace
+
+Fill each section with code plan data from Step 4.
+
+> ⚠️ **CRITICAL CONSTRAINTS:**
+> - **FORBIDDEN: `create_file` to rewrite the entire document**
+> - **MUST use `search_replace` to fill each section individually**
+> - **All section titles MUST be preserved**
+
+**Section Filling Guide:**
+
+| Section | Content Source |
+|---------|---------------|
+| **File-to-TestCase Mapping** | From Step 4.4 |
+| **Mock Strategy** | From Step 4.3 |
+| **Shared Resources** | From Step 4.2 |
+| **Test File Structure** | From Step 4.1 |
 
 ### Document Purpose
 
@@ -282,10 +319,6 @@ Output the code plan document for traceability:
 - Provides reference for future test maintenance
 - Enables traceability from test code to test cases
 
-### Template Reference
-
-Use: `speccrew-test-code-gen/templates/TEST-CODE-PLAN-TEMPLATE.md`
-
 # Key Rules
 
 | Rule | Description |

package/.speccrew/skills/speccrew-test-execute/SKILL.md

@@ -12,6 +12,16 @@ tools: Read, Write, Glob, Grep, Terminal
 
 # Workflow
 
+## Absolute Constraints
+
+> **These rules apply to ALL document generation steps. Violation = task failure.**
+
+1. **FORBIDDEN: `create_file` for documents** — NEVER use `create_file` to write test reports or bug reports. Documents MUST be created by copying the template then filling sections with `search_replace`.
+
+2. **FORBIDDEN: Full-file rewrite** — NEVER replace the entire document content in a single operation. Always use targeted `search_replace` on specific sections.
+
+3. **MANDATORY: Template-first workflow** — Copy template MUST execute before filling sections.
+
 ## Step 1: Read Inputs
 
 Read the following documents in order:
@@ -179,43 +189,33 @@ For each deviation, analyze:
 
 Read template: `speccrew-test-execute/templates/TEST-REPORT-TEMPLATE.md`
 
-### 6.2 Fill Report Content
-
-Generate comprehensive test report including:
-
-**Execution Summary**:
-- Feature name and platform
-- Test framework and version
-- Execution date and duration
-- Overall pass rate
+### 6.2 Copy Template to Report Path
 
-**Results Overview**:
-- Counts and percentages for all result types
-- Visual pass/fail indication
+1. **Read template** from Step 6.1
+2. **Replace top-level placeholders** (feature name, platform, execution date, etc.)
+3. **Create the document** using `create_file` at: `{output_dir}/{feature}-test-report.md`
+4. **Verify**: Document has complete section structure
 
-**Results by Test Dimension**:
-- Breakdown by test type (happy path, boundary, exception, etc.)
-- Pass rate per dimension
+### 6.3 Fill Each Section Using search_replace
 
-**Failed Test Details**:
-- Table of all failed tests
-- Links to corresponding bug reports
+Fill each section with test execution data.
 
-**Coverage Status**:
-- Requirement-to-test-case mapping
-- Status per requirement
+> ⚠️ **CRITICAL CONSTRAINTS:**
+> - **FORBIDDEN: `create_file` to rewrite the entire document**
+> - **MUST use `search_replace` to fill each section individually**
+> - **All section titles MUST be preserved**
 
-**Environment Information**:
-- OS, runtime, framework versions
-- Key dependencies
+**Section Filling Guide:**
 
-**Recommendations**:
-- Priority fixes needed
-- Suggested next steps
-
-### 6.3 Write Report
-
-Output path: `{output_dir}/{feature}-test-report.md`
+| Section | Content |
+|---------|---------|
+| **Execution Summary** | Feature name and platform, test framework and version, execution date and duration, overall pass rate |
+| **Results Overview** | Counts and percentages for all result types, visual pass/fail indication |
+| **Results by Test Dimension** | Breakdown by test type (happy path, boundary, exception, etc.), pass rate per dimension |
+| **Failed Test Details** | Table of all failed tests, links to corresponding bug reports |
+| **Coverage Status** | Requirement-to-test-case mapping, status per requirement |
+| **Environment Information** | OS, runtime, framework versions, key dependencies |
+| **Recommendations** | Priority fixes needed, suggested next steps |
 
 ## Step 7: Generate Bug Reports
 
@@ -223,9 +223,22 @@ Output path: `{output_dir}/{feature}-test-report.md`
 
 Read template: `speccrew-test-execute/templates/BUG-REPORT-TEMPLATE.md`
 
-### 7.2 Create Individual Bug Reports
+### 7.2 Copy Template for Each Bug Report
 
 For each FAIL type failure:
+1. **Read template** from Step 7.1: `templates/BUG-REPORT-TEMPLATE.md`
+2. **Replace top-level placeholders** (Bug ID, feature name, TC ID)
+3. **Create document** using `create_file` at: `{output_dir}/bugs/{feature}-bug-{seq}.md`
+
+### 7.3 Fill Each Bug Report Using search_replace
+
+For each bug report created in 7.2, fill sections using `search_replace`:
+
+> ⚠️ **CRITICAL CONSTRAINTS:**
+> - **FORBIDDEN: `create_file` to rewrite the entire document**
+> - **MUST use `search_replace` to fill each section individually**
+
+**Section Filling Guide:**
 
 1. **Assign Bug ID**: `BUG-{feature}-{seq}` (sequential numbering)
 
@@ -246,10 +259,7 @@ For each FAIL type failure:
    - Relevant error log excerpt
    - Suggested fix direction
 
-4. **Write Individual File**:
-   Output path: `{output_dir}/bugs/{feature}-bug-{seq}.md`
-
-### 7.3 Bug Report Quality Checklist
+### 7.4 Bug Report Quality Checklist
 
 Each bug report must include:
 - [ ] Unique Bug ID

package/package.json

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