cc-discipline 2.6.0 → 2.6.1
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
|
@@ -42,14 +42,22 @@ Pause and honestly answer every question below. Do NOT skip any. Do NOT rational
|
|
|
42
42
|
|
|
43
43
|
- When was `docs/progress.md` last updated?
|
|
44
44
|
- If a compact happened RIGHT NOW, could a fresh Claude resume from progress.md alone?
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
-
|
|
52
|
-
|
|
45
|
+
|
|
46
|
+
### 5a. Working Context (check each):
|
|
47
|
+
- **Key Commands** — are all build/test/deploy commands listed? Not "run tests" but the exact command with flags and paths.
|
|
48
|
+
- **Current Workflow** — is the step-by-step process documented? e.g., "1. edit schema → 2. run migrate → 3. run tests" with exact commands.
|
|
49
|
+
- **Tools & Scripts** — any helpers or scripts developed this session? Include file path and what it does.
|
|
50
|
+
- **Environment State** — what's running, what ports, what branch? e.g., "Docker on :5432, branch feature/auth"
|
|
51
|
+
- **Gotchas** — any traps or workarounds discovered? e.g., "pytest must run from /src not root"
|
|
52
|
+
|
|
53
|
+
### 5b. Milestones (check each completed milestone has):
|
|
54
|
+
- **What** — what was accomplished (2-3 sentences, not one-liners)
|
|
55
|
+
- **How** — approach taken, key files changed, commands used
|
|
56
|
+
- **Why this approach** — why this way, what alternatives were rejected
|
|
57
|
+
- **Gotchas** — what went wrong or was surprising
|
|
58
|
+
- **Verification** — how it was confirmed working (test output, manual check)
|
|
59
|
+
|
|
60
|
+
If ANY of the above are stale, empty, or one-liner lazy: **update docs/progress.md NOW before continuing.** This takes 2 minutes and saves hours of re-discovery after compact.
|
|
53
61
|
|
|
54
62
|
## 6. Status report
|
|
55
63
|
|
|
@@ -44,7 +44,22 @@
|
|
|
44
44
|
|
|
45
45
|
## Milestones
|
|
46
46
|
|
|
47
|
-
<!-- Claude: append a record below after completing each milestone
|
|
47
|
+
<!-- Claude: append a record below after completing each milestone.
|
|
48
|
+
DON'T just write one sentence. Each milestone should capture enough
|
|
49
|
+
detail that a future session can learn from it, not just know it happened.
|
|
50
|
+
Use the template below. -->
|
|
51
|
+
|
|
52
|
+
<!-- TEMPLATE (copy and fill for each milestone):
|
|
53
|
+
|
|
54
|
+
### [date] — [milestone title]
|
|
55
|
+
|
|
56
|
+
**What**: [what was accomplished, 2-3 sentences]
|
|
57
|
+
**How**: [approach taken, key files changed, commands used]
|
|
58
|
+
**Why this approach**: [why this way and not another — rejected alternatives]
|
|
59
|
+
**Gotchas**: [what went wrong, what was surprising, workarounds]
|
|
60
|
+
**Verification**: [how we confirmed it works — test output, manual check]
|
|
61
|
+
|
|
62
|
+
-->
|
|
48
63
|
|
|
49
64
|
---
|
|
50
65
|
|