cc-dev-template 0.1.8 → 0.1.9

package/package.json

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

package/src/agents/claude-md-agent.md

@@ -28,7 +28,7 @@ When given insights to document:
 
 ## ADR vs CLAUDE.md
 
-Reject content that should be an ADR instead.
+Route ADR-worthy content to adr-agent instead.
 
 | CLAUDE.md (Operational How-To) | ADR (Architectural Decision) |
 |-------------------------------|------------------------------|

package/src/agents/execution-agent.md

@@ -130,7 +130,7 @@ The prompting skill ensures your prompts follow established patterns: explaining
 - **Missing Dependency** - Need something from an upstream task that wasn't done
 - **Blocked** - External factor prevents completion (missing API key, service down, etc.)
 
-**Do not try to work around issues.** The plan should have removed all ambiguity. If something is unexpected, escalate.
+**Stop and escalate when unexpected issues arise.** The plan should have removed all ambiguity. If something is unexpected, escalate.
 
 When escalating, report:
 - What you encountered
@@ -145,4 +145,4 @@ When escalating, report:
 
 **Outcome is context** - Write outcomes for the next person (or agent). What did you do? Where are things? What decisions did you make?
 
-**No improvisation** - If the task or plan is unclear, escalate. Don't guess.
+**Escalate when unclear** - If the task or plan is unclear, escalate rather than guessing.

package/src/agents/tdd-agent.md

@@ -156,7 +156,7 @@ Report:
 
 **Tests are specifications.** In fix mode, the test defines correct behavior. Don't question it—make the code conform.
 
-**Fix mode: code only.** Never touch test files in fix mode. If the test is wrong, escalate.
+**Fix mode: code only.** Modify only non-test files in fix mode. If the test is wrong, escalate.
 
 **Test mode: fail is success.** A test that fails (because the bug exists) is exactly what we want. A passing test means the hypothesis is wrong.
 

package/src/skills/create-agent-skills/references/principles.md

@@ -81,6 +81,27 @@ After writing SKILL.md, ask: **"If Claude reads this right now, does it know wha
 
 If the answer is "it would understand what the skill is about" but not "it would know what to do," rewrite it.
 
+### Agent Prompts Are Different
+
+The red flags above apply to SKILL.md files, not agent prompts. Agent prompts and skills have different characteristics:
+
+| Aspect | Agent Prompt | SKILL.md |
+|--------|--------------|----------|
+| When read | Once per spawn | Repeatedly during session |
+| Purpose | Provide context for focused task | Route to workflows |
+| WHY/WHO/SUCCESS | Appropriate—crucial context | Red flag—wastes tokens |
+| Lifespan | Single invocation | Entire user session |
+
+Agent prompts benefit from a Purpose section with WHY/WHO/SUCCESS because:
+- Agents spawn for a single focused task and need full context upfront
+- The context is read once, not repeatedly
+- Understanding purpose helps agents make better decisions
+
+Skills should route to actions immediately because:
+- Users interact with skills throughout a session
+- Meta-descriptions consume tokens on every activation
+- Instructions are more valuable than context in repeated interactions
+
 ## Progressive Disclosure
 
 ### The Problem Without It

package/src/skills/orchestration/scripts/plan-status.js

@@ -129,6 +129,11 @@ function getPlanInfo(planDir, slug) {
     const taskCounts = countTasks(manifest);
     if (taskCounts) {
       planInfo.tasks = taskCounts;
+
+      // Derive completion status: if all tasks are completed, the plan is completed
+      if (taskCounts.total > 0 && taskCounts.completed === taskCounts.total) {
+        planInfo.status = 'completed';
+      }
     }
   }