cc-dev-template 0.1.38 → 0.1.40

package/package.json

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

package/src/commands/done.md

@@ -1,52 +1,76 @@
 ---
 description: End a session - sync documentation and commit work
+argument-hint: [next task]
 ---
 
 # Session Closeout
 
-Capture what was accomplished so the next session starts with accurate context.
+Bridge the gap between this session and the next. Git captures what was done; CURRENT_WORK.md captures what to do next.
 
 ## Why This Matters
 
-You have full conversation context that will be lost when this session ends. The next session (or another developer) will only have git history and documentation. Your job is to bridge that gap.
+CURRENT_WORK.md is read at the start of every session. It should answer one question: "What should I work on?"
+
+Git commits are the historical record of completed work. There's no need to duplicate that in documentation.
 
 ## Execute Directly
 
-This requires full conversation context. Handle it yourself rather than delegating to a sub-agent.
+This requires full conversation context. Handle it yourself rather than delegating.
+
+## Steps
+
+**1. Run code simplifier (if available)**
+
+If the `code-simplifier` subagent is available (it's a plugin, not always present), run it on your staged changes before committing. This automatically refines code for clarity and consistency.
 
-## What To Do
+- Check if you have access to the `code-simplifier` subagent type
+- If available and there are staged changes, invoke it targeting those files
+- If the agent isn't available, skip this step silently and proceed to commit
+- After simplification, run the build and any tests as a sanity check to ensure nothing broke
+- If tests/build fail, fix the issues before proceeding to commit
 
-**1. Understand what happened this session**
+**2. Commit your work**
 
-Review git commits made during this session and recall what was discussed/decided in conversation. The combination of commits + conversation = full picture of accomplishments.
+Write clear commit messages that explain what was accomplished. This IS your record of completed work.
 
-**2. Update `docs/CURRENT_WORK.md`**
+**3. Update `docs/CURRENT_WORK.md`**
 
-Sync the document with reality:
-- Move completed items to "Recently Completed"
-- Update "In Progress" with current state
-- Adjust "Up Next" based on what was learned
-- Note any new blockers
+This file is forward-looking. Review it holistically and ensure it contains ONLY:
 
-**3. Capture workflow discoveries (rarely)**
+- **Up Next** — Tasks to tackle in future sessions. If the user specified a next task ($ARGUMENTS), add it here.
+- **In Progress** — Work that's partially done and needs continuation
+- **Blocked / Waiting** — Items waiting on external input (people, services, decisions)
+- **Open Questions** — Unanswered questions that need follow-up
 
-Consider: Did I learn something that would save time in future sessions?
+**Remove** anything that doesn't require future action:
+- Completed work (that's in git now)
+- Answered questions (document answers in appropriate docs if needed, then remove from here)
+- Historical context or architecture notes (move to relevant docs/)
+- Status updates about past sessions
 
-Add to CLAUDE.md only for high-value operational knowledge:
-- Dev commands, ports, local URLs, credentials
+The file should be scannable in 30 seconds. If it takes longer, it's too long.
+
+**4. Capture workflow discoveries (rarely)**
+
+Add to CLAUDE.md only high-value operational knowledge that can't be found by reading code:
+- Dev commands, ports, local URLs
 - Key paths (logs, config, seed data)
 - Non-obvious project conventions
 
-This is knowledge that can't be found by reading code. Most sessions: add nothing. When adding, keep it minimal and scannable.
+Most sessions: add nothing.
+
+**5. Push**
 
-**4. Commit and push**
+Push your commits to the remote.
 
-Write a commit message that reflects what was actually accomplished this session. Include both docs/ and any other modified files.
+**6. Report what was updated**
 
-**5. Report what was updated**
+Summarize: commits made, CURRENT_WORK.md changes, any items removed/added.
 
 ## Mental Model
 
-- **CLAUDE.md** = context loader, rarely changes
-- **CURRENT_WORK.md** = living status, changes every session
-- **Git history** = code changes speak for themselves
+| File | Purpose | Changes |
+|------|---------|---------|
+| Git history | What was done | Every session |
+| CURRENT_WORK.md | What to do next | Every session (kept minimal) |
+| CLAUDE.md | How to work here | Rarely |

package/src/skills/initialize-project/SKILL.md

@@ -36,17 +36,17 @@ Create the minimal scaffolding that enables the `/prime` and `/done` workflow. T
    ```markdown
    # Current Work
 
-   ## Recently Completed
-   - Initial project setup
-
    ## In Progress
-   - (none yet)
+   - (none)
 
    ## Up Next
    - (add your first task)
 
    ## Blocked / Waiting
    - (none)
+
+   ## Open Questions
+   - (none)
    ```
 
 4. **Handle CLAUDE.md:**