cc-dev-template 0.1.38 → 0.1.40
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
package/src/commands/done.md
CHANGED
|
@@ -1,52 +1,76 @@
|
|
|
1
1
|
---
|
|
2
2
|
description: End a session - sync documentation and commit work
|
|
3
|
+
argument-hint: [next task]
|
|
3
4
|
---
|
|
4
5
|
|
|
5
6
|
# Session Closeout
|
|
6
7
|
|
|
7
|
-
|
|
8
|
+
Bridge the gap between this session and the next. Git captures what was done; CURRENT_WORK.md captures what to do next.
|
|
8
9
|
|
|
9
10
|
## Why This Matters
|
|
10
11
|
|
|
11
|
-
|
|
12
|
+
CURRENT_WORK.md is read at the start of every session. It should answer one question: "What should I work on?"
|
|
13
|
+
|
|
14
|
+
Git commits are the historical record of completed work. There's no need to duplicate that in documentation.
|
|
12
15
|
|
|
13
16
|
## Execute Directly
|
|
14
17
|
|
|
15
|
-
This requires full conversation context. Handle it yourself rather than delegating
|
|
18
|
+
This requires full conversation context. Handle it yourself rather than delegating.
|
|
19
|
+
|
|
20
|
+
## Steps
|
|
21
|
+
|
|
22
|
+
**1. Run code simplifier (if available)**
|
|
23
|
+
|
|
24
|
+
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.
|
|
16
25
|
|
|
17
|
-
|
|
26
|
+
- Check if you have access to the `code-simplifier` subagent type
|
|
27
|
+
- If available and there are staged changes, invoke it targeting those files
|
|
28
|
+
- If the agent isn't available, skip this step silently and proceed to commit
|
|
29
|
+
- After simplification, run the build and any tests as a sanity check to ensure nothing broke
|
|
30
|
+
- If tests/build fail, fix the issues before proceeding to commit
|
|
18
31
|
|
|
19
|
-
**
|
|
32
|
+
**2. Commit your work**
|
|
20
33
|
|
|
21
|
-
|
|
34
|
+
Write clear commit messages that explain what was accomplished. This IS your record of completed work.
|
|
22
35
|
|
|
23
|
-
**
|
|
36
|
+
**3. Update `docs/CURRENT_WORK.md`**
|
|
24
37
|
|
|
25
|
-
|
|
26
|
-
- Move completed items to "Recently Completed"
|
|
27
|
-
- Update "In Progress" with current state
|
|
28
|
-
- Adjust "Up Next" based on what was learned
|
|
29
|
-
- Note any new blockers
|
|
38
|
+
This file is forward-looking. Review it holistically and ensure it contains ONLY:
|
|
30
39
|
|
|
31
|
-
**
|
|
40
|
+
- **Up Next** — Tasks to tackle in future sessions. If the user specified a next task ($ARGUMENTS), add it here.
|
|
41
|
+
- **In Progress** — Work that's partially done and needs continuation
|
|
42
|
+
- **Blocked / Waiting** — Items waiting on external input (people, services, decisions)
|
|
43
|
+
- **Open Questions** — Unanswered questions that need follow-up
|
|
32
44
|
|
|
33
|
-
|
|
45
|
+
**Remove** anything that doesn't require future action:
|
|
46
|
+
- Completed work (that's in git now)
|
|
47
|
+
- Answered questions (document answers in appropriate docs if needed, then remove from here)
|
|
48
|
+
- Historical context or architecture notes (move to relevant docs/)
|
|
49
|
+
- Status updates about past sessions
|
|
34
50
|
|
|
35
|
-
|
|
36
|
-
|
|
51
|
+
The file should be scannable in 30 seconds. If it takes longer, it's too long.
|
|
52
|
+
|
|
53
|
+
**4. Capture workflow discoveries (rarely)**
|
|
54
|
+
|
|
55
|
+
Add to CLAUDE.md only high-value operational knowledge that can't be found by reading code:
|
|
56
|
+
- Dev commands, ports, local URLs
|
|
37
57
|
- Key paths (logs, config, seed data)
|
|
38
58
|
- Non-obvious project conventions
|
|
39
59
|
|
|
40
|
-
|
|
60
|
+
Most sessions: add nothing.
|
|
61
|
+
|
|
62
|
+
**5. Push**
|
|
41
63
|
|
|
42
|
-
|
|
64
|
+
Push your commits to the remote.
|
|
43
65
|
|
|
44
|
-
|
|
66
|
+
**6. Report what was updated**
|
|
45
67
|
|
|
46
|
-
|
|
68
|
+
Summarize: commits made, CURRENT_WORK.md changes, any items removed/added.
|
|
47
69
|
|
|
48
70
|
## Mental Model
|
|
49
71
|
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
72
|
+
| File | Purpose | Changes |
|
|
73
|
+
|------|---------|---------|
|
|
74
|
+
| Git history | What was done | Every session |
|
|
75
|
+
| CURRENT_WORK.md | What to do next | Every session (kept minimal) |
|
|
76
|
+
| CLAUDE.md | How to work here | Rarely |
|
|
@@ -36,17 +36,17 @@ Create the minimal scaffolding that enables the `/prime` and `/done` workflow. T
|
|
|
36
36
|
```markdown
|
|
37
37
|
# Current Work
|
|
38
38
|
|
|
39
|
-
## Recently Completed
|
|
40
|
-
- Initial project setup
|
|
41
|
-
|
|
42
39
|
## In Progress
|
|
43
|
-
- (none
|
|
40
|
+
- (none)
|
|
44
41
|
|
|
45
42
|
## Up Next
|
|
46
43
|
- (add your first task)
|
|
47
44
|
|
|
48
45
|
## Blocked / Waiting
|
|
49
46
|
- (none)
|
|
47
|
+
|
|
48
|
+
## Open Questions
|
|
49
|
+
- (none)
|
|
50
50
|
```
|
|
51
51
|
|
|
52
52
|
4. **Handle CLAUDE.md:**
|