cc-dev-template 0.1.80 → 0.1.81

package/src/skills/task-review/SKILL.md

@@ -7,7 +7,7 @@ context: fork
 
 # Task Review
 
-Review the task breakdown to catch issues before implementation begins.
+Review the task breakdown, auto-fix all issues found, and report what was fixed.
 
 ## What To Do Now
 
@@ -15,4 +15,4 @@ If an argument was provided, use it as the spec name. Otherwise, find the most r
 
 Read the spec file and all task files in the `tasks/` directory.
 
-Then read `references/checklist.md` and evaluate each item.
+Then read `references/checklist.md` and run the review-and-fix loop.

package/src/skills/task-review/references/checklist.md

@@ -1,9 +1,9 @@
 # Task Review Checklist
 
-Evaluate each area. For each issue found, note the severity:
-- **Critical**: Must fix before implementation
-- **Warning**: Should fix, but could proceed
-- **Note**: Minor suggestion
+Evaluate each area. Fix every issue you find by editing the task files directly. Note what you found and fixed:
+- **Critical**: Must fix — fix immediately
+- **Warning**: Should fix — fix now
+- **Note**: Minor suggestion — fix if straightforward
 
 ## 1. Coverage
 
@@ -132,24 +132,22 @@ Compare files-to-create across all tasks. Group by similarity (naming patterns,
 
 ---
 
-## Output Format
+## Review and Fix Loop
 
-Return findings as a structured list:
+Run the checklist above against all task files. Fix every issue you find by editing the task files directly. Then re-run the full checklist from the top. Repeat until no issues remain.
 
-```
-## Critical Issues
-- [T002] Depends on T005 which comes later - wrong order
-- [T003] Missing verification method
+## Output Format
 
-## Warnings
-- [T001] touches 12 files - consider splitting
-- Criterion "User can delete account" has no corresponding task
+After all issues are fixed, report what you found and fixed:
 
-## Notes
-- [T004] Could merge with T005 since they share the same files
+```
+## Review Summary
+- [T002] Fixed: reordered dependency — was depending on T005 which came later
+- [T003] Fixed: added concrete verification command (was missing)
+- [T001] Fixed: split into T001a/T001b — was touching 12 files
 
 ## Skill Observations (optional)
-If any checklist items, severity criteria, or review patterns in this skill were wrong, incomplete, or misleading during this review, note them here. Leave empty if no issues were found.
+If any checklist items or review patterns in this skill were wrong or misleading, note them here.
 ```
 
 If no issues found, state: "Task breakdown looks good. All criteria covered, dependencies valid, verification methods concrete."

package/src/skills/execute-spec/references/workflow.md

@@ -1,82 +0,0 @@
-# Execute Spec Workflow
-
-## Overview
-
-```
-PHASE 1: HYDRATE
-  Run parse script → TaskCreate with dependencies
-  (NO file reading by orchestrator)
-
-PHASE 2: BUILD
-  Loop: find unblocked tasks → dispatch spec-implementer → receive minimal status
-  Continue until all tasks built
-
-PHASE 3: VALIDATE
-  Dispatch spec-validator for each task (all in parallel)
-  Receive pass/fail status only
-
-PHASE 4: TRIAGE
-  For failed tasks: re-dispatch spec-implementer
-  Re-validate
-  Loop until clean or user defers
-
-PHASE 5: REFLECT
-  Assess orchestration experience → improve skill files
-  (Mandatory — workflow is NOT complete without this)
-```
-
-## Critical: Minimal Context
-
-**Agent returns are pass/fail only.** All details go in task files.
-
-- Implementer returns: `Task complete: T005` or `Blocked: T005 - reason`
-- Validator returns: `Pass: T005` or `Issues: T005 - [brief list]`
-
-The orchestrator never reads task files. It dispatches paths and receives status.
-
-## Phase 1: Hydrate
-
-Read `phase-1-hydrate.md` for details.
-
-Use the parse script to get task metadata:
-```bash
-node ~/.claude/scripts/parse-task-files.js {spec-path}
-```
-
-This returns JSON with task IDs, titles, dependencies, and paths. Create tasks from this output without reading any files.
-
-## Phase 2: Build
-
-Read `phase-2-build.md` for details.
-
-1. Find unblocked tasks via TaskList
-2. Dispatch spec-implementer with just the file path
-3. Receive minimal status (pass/fail)
-4. Repeat until all built
-
-## Phase 3: Validate
-
-Read `phase-3-validate.md` for details.
-
-1. Dispatch spec-validator for each task (parallel)
-2. Receive pass/fail status
-3. Collect list of failed task IDs
-
-## Phase 4: Triage
-
-Read `phase-4-triage.md` for details.
-
-1. For failed tasks: re-dispatch spec-implementer (it reads Review Notes and fixes)
-2. Re-run spec-validator on fixed tasks
-3. Loop until all pass or user defers remaining issues
-
-## Key Principles
-
-- **No file reading by orchestrator** - Hook blocks task file reads
-- **Minimal returns** - Agents return status only, details in task files
-- **Task file is source of truth** - Implementation Notes and Review Notes track all history
-- **Parallelism** - Use `run_in_background: true` where possible
-
-**IMPORTANT: You are not done. You MUST read and complete the next step. The workflow is incomplete without it.**
-
-Read `references/phase-5-reflect.md` now.