cc-dev-template 0.1.87 → 0.1.88

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-dev-template",
-  "version": "0.1.87",
+  "version": "0.1.88",
   "description": "Structured AI-assisted development framework for Claude Code",
   "bin": {
     "cc-dev-template": "./bin/install.js"

package/src/agents/spec-writer.md

@@ -28,7 +28,10 @@ When prompted to review a spec:
 2. Run every check in the review checklist below
 3. Fix every issue found directly in spec.md — do not report issues, fix them
 4. After fixing, re-run the checklist to verify
-5. Return APPROVED if all checks pass, or report remaining issues that could not be auto-fixed
+5. Return one of three verdicts:
+   - **APPROVED** — zero issues found on any check. The spec is clean.
+   - **APPROVED_WITH_FIXES** — issues were found and fixed. Another reviewer must verify the fixes.
+   - **ISSUES REMAINING** — unfixable issues exist (e.g., missing prerequisites that need user action).
 
 ## Spec Format
 
@@ -143,14 +146,24 @@ Sections:
 - Out of Scope: N exclusions
 ```
 
-**Review mode (all checks pass):**
+**Review mode (zero issues found — clean pass):**
 ```
 APPROVED
 
-N issues found and fixed.
+0 issues found.
 All 12 checks passed.
 ```
 
+**Review mode (issues found and fixed — needs re-review):**
+```
+APPROVED_WITH_FIXES
+
+N issues found and fixed:
+- [Check Name]: what was fixed
+...
+All 12 checks now pass, but fixes need verification by a fresh reviewer.
+```
+
 **Review mode (unfixable issues remain):**
 ```
 ISSUES REMAINING

package/src/agents/task-breakdown.md

@@ -28,7 +28,10 @@ When prompted to review a task breakdown:
 3. Run every check in the review checklist below
 4. Fix every issue found directly in the task files — do not report issues, fix them
 5. After fixing, re-run the checklist to verify
-6. Return APPROVED if all checks pass, or report remaining issues that could not be auto-fixed
+6. Return one of three verdicts:
+   - **APPROVED** — zero issues found on any check. The breakdown is clean.
+   - **APPROVED_WITH_FIXES** — issues were found and fixed. Another reviewer must verify the fixes.
+   - **ISSUES REMAINING** — unfixable issues exist that need user action.
 
 ## Task File Format
 
@@ -112,15 +115,26 @@ Created N task files in {spec_dir}/tasks/:
 Dependency chain: T001 → T002 → T003
 ```
 
-**Review mode (all checks pass):**
+**Review mode (zero issues found — clean pass):**
 ```
 APPROVED
 
 N tasks reviewed against M acceptance criteria.
-N issues found and fixed.
+0 issues found.
 All 9 checks passed.
 ```
 
+**Review mode (issues found and fixed — needs re-review):**
+```
+APPROVED_WITH_FIXES
+
+N tasks reviewed against M acceptance criteria.
+N issues found and fixed:
+- [Check Name]: what was fixed
+...
+All 9 checks now pass, but fixes need verification by a fresh reviewer.
+```
+
 **Review mode (unfixable issues remain):**
 ```
 ISSUES REMAINING

package/src/skills/ship/references/step-5-spec.md

@@ -1,6 +1,6 @@
 # Spec Generation
 
-The orchestrator spawns a spec-writer agent to generate the spec, then spawns a fresh instance of the same agent to review and fix it. Each review is a clean context window — the reviewer didn't write the spec, so it reads with fresh eyes. Loop until the reviewer returns APPROVED.
+The orchestrator spawns a spec-writer agent to generate the spec, then spawns a fresh instance of the same agent to review and fix it. Each review is a clean context window — the reviewer didn't write the spec, so it reads with fresh eyes. Loop until a reviewer finds zero issues — if a reviewer fixes issues, those fixes must be verified by another fresh reviewer.
 
 The spec is the last line of defense. Any error or ambiguity here multiplies through task breakdown and implementation.
 
@@ -43,14 +43,16 @@ Spawn a FRESH instance of spec-writer in review mode:
 ```
 Agent tool:
   subagent_type: "spec-writer"
-  prompt: "Review the spec at {spec_dir}/spec.md against the upstream artifacts (intent.md, research.md, design.md). Run the full 12-point checklist. Fix every issue you find directly in spec.md. Return APPROVED if all checks pass, or ISSUES REMAINING for anything you cannot auto-fix."
+  prompt: "Review the spec at {spec_dir}/spec.md against the upstream artifacts (intent.md, research.md, design.md). Run the full 12-point checklist. Fix every issue you find directly in spec.md. Return APPROVED if zero issues found, APPROVED_WITH_FIXES if issues were found and fixed, or ISSUES REMAINING for anything you cannot auto-fix."
 ```
 
-**If APPROVED**: Move to Task 4.
+**If APPROVED** (zero issues found): The spec is verified clean. Move to Task 4.
+
+**If APPROVED_WITH_FIXES**: The reviewer fixed issues, but those fixes have not been verified. Spawn another fresh instance to review again. Continue until a reviewer returns APPROVED with zero issues.
 
 **If ISSUES REMAINING**: Spawn another fresh instance to review again. The previous reviewer already fixed what it could — the next reviewer may catch different things or resolve what the last one couldn't.
 
-If the loop runs more than 3 cycles without APPROVED, present the remaining issues to the user and ask how to proceed.
+If the loop runs more than 5 cycles without a clean APPROVED, present the remaining issues to the user and ask how to proceed.
 
 ## Task 4: Review With User
 

package/src/skills/ship/references/step-6-tasks.md

@@ -1,6 +1,6 @@
 # Task Breakdown
 
-The orchestrator spawns a task-breakdown agent to generate task files, then spawns a fresh instance of the same agent to review and fix them. Each review is a clean context window — the reviewer didn't write the tasks, so it reads with fresh eyes. Loop until the reviewer returns APPROVED.
+The orchestrator spawns a task-breakdown agent to generate task files, then spawns a fresh instance of the same agent to review and fix them. Each review is a clean context window — the reviewer didn't write the tasks, so it reads with fresh eyes. Loop until a reviewer finds zero issues — if a reviewer fixes issues, those fixes must be verified by another fresh reviewer.
 
 Read `{spec_dir}/spec.md` before proceeding.
 
@@ -30,14 +30,16 @@ Spawn a FRESH instance of task-breakdown in review mode:
 ```
 Agent tool:
   subagent_type: "task-breakdown"
-  prompt: "Review the task breakdown at {spec_dir}. Read spec.md and all files in {spec_dir}/tasks/. Run the full 9-point checklist. Fix every issue you find directly in the task files. Return APPROVED if all checks pass, or ISSUES REMAINING for anything you cannot auto-fix."
+  prompt: "Review the task breakdown at {spec_dir}. Read spec.md and all files in {spec_dir}/tasks/. Run the full 9-point checklist. Fix every issue you find directly in the task files. Return APPROVED if zero issues found, APPROVED_WITH_FIXES if issues were found and fixed, or ISSUES REMAINING for anything you cannot auto-fix."
 ```
 
-**If APPROVED**: Move to Task 3.
+**If APPROVED** (zero issues found): The breakdown is verified clean. Move to Task 3.
+
+**If APPROVED_WITH_FIXES**: The reviewer fixed issues, but those fixes have not been verified. Spawn another fresh instance to review again. Continue until a reviewer returns APPROVED with zero issues.
 
 **If ISSUES REMAINING**: Spawn another fresh instance to review again. The previous reviewer already fixed what it could — the next reviewer may catch different things or resolve what the last one couldn't.
 
-If the loop runs more than 3 cycles without APPROVED, present the remaining issues to the user and ask how to proceed.
+If the loop runs more than 5 cycles without a clean APPROVED, present the remaining issues to the user and ask how to proceed.
 
 ## Task 3: Review With User