cc-discipline 2.4.0 → 2.5.0

package/init.sh

@@ -362,11 +362,13 @@ cp -r "$SCRIPT_DIR/templates/.claude/skills/self-check" .claude/skills/
 cp -r "$SCRIPT_DIR/templates/.claude/skills/evaluate" .claude/skills/
 cp -r "$SCRIPT_DIR/templates/.claude/skills/think" .claude/skills/
 cp -r "$SCRIPT_DIR/templates/.claude/skills/retro" .claude/skills/
+cp -r "$SCRIPT_DIR/templates/.claude/skills/summary" .claude/skills/
 echo "   ✓ /commit — smart commit (test → update memory → commit)"
 echo "   ✓ /self-check — periodic discipline check (use with /loop 10m /self-check)"
 echo "   ✓ /evaluate — evaluate external review/advice against codebase context"
 echo "   ✓ /think — stop and think before coding (ask → propose → wait)"
 echo "   ✓ /retro — post-task retrospective (project + framework feedback)"
+echo "   ✓ /summary — write high-quality compact option before /compact"
 
 # ─── Handle CLAUDE.md ───
 if [ ! -f "CLAUDE.md" ]; then
@@ -477,6 +479,7 @@ if [ "$INSTALL_MODE" = "fresh" ]; then
     echo -e "  ${GREEN}.claude/skills/evaluate/${NC}     ← /evaluate assess external review advice"
     echo -e "  ${GREEN}.claude/skills/think/${NC}        ← /think stop and think before coding"
     echo -e "  ${GREEN}.claude/skills/retro/${NC}        ← /retro post-task retrospective"
+    echo -e "  ${GREEN}.claude/skills/summary/${NC} ← /summary before compacting"
     echo -e "  ${GREEN}.claude/settings.json${NC}        ← Hooks configuration"
     echo -e "  ${GREEN}docs/progress.md${NC}             ← Progress log (maintained by Claude)"
     echo -e "  ${GREEN}docs/debug-log.md${NC}            ← Debug log (maintained by Claude)"
@@ -497,6 +500,7 @@ else
     echo -e "  ${GREEN}.claude/skills/evaluate/${NC}     ← /evaluate external review assessment"
     echo -e "  ${GREEN}.claude/skills/think/${NC}        ← /think stop and think before coding"
     echo -e "  ${GREEN}.claude/skills/retro/${NC}        ← /retro post-task retrospective"
+    echo -e "  ${GREEN}.claude/skills/summary/${NC} ← /summary before compacting"
     if [ ! -f "$BACKUP_DIR/settings.json" ] || [ -f ".claude/.cc-discipline-settings-template.json" ]; then
         echo -e "  ${YELLOW}.claude/settings.json${NC}        ← See notes above"
     else

package/lib/doctor.sh

@@ -95,7 +95,7 @@ done
 # 6. Skills
 echo ""
 echo "Skills:"
-for skill in commit self-check evaluate think retro; do
+for skill in commit self-check evaluate think retro summary; do
     if [ -d ".claude/skills/${skill}" ]; then
         ok "/${skill}"
     else

package/lib/status.sh

@@ -71,8 +71,9 @@ SKILLS=""
 [ -d ".claude/skills/evaluate" ] && SKILLS="${SKILLS}/evaluate "
 [ -d ".claude/skills/think" ] && SKILLS="${SKILLS}/think "
 [ -d ".claude/skills/retro" ] && SKILLS="${SKILLS}/retro "
+[ -d ".claude/skills/summary" ] && SKILLS="${SKILLS}/summary "
 SKILL_COUNT=$(echo "$SKILLS" | wc -w | tr -d ' ')
-echo -e "${GREEN}${SKILL_COUNT}/5${NC} (${SKILLS% })"
+echo -e "${GREEN}${SKILL_COUNT}/6${NC} (${SKILLS% })"
 
 # Settings
 echo -n "Settings: "

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-discipline",
-  "version": "2.4.0",
+  "version": "2.5.0",
   "description": "Discipline framework for Claude Code — rules, hooks, and agents that keep AI on track",
   "bin": {
     "cc-discipline": "bin/cli.sh"

package/templates/.claude/hooks/action-counter.sh

@@ -29,7 +29,7 @@ fi
 
 if [ $((COUNT % THRESHOLD)) -eq 0 ]; then
     cat <<JSONEOF
-{"hookSpecificOutput":{"hookEventName":"PreToolUse","additionalContext":"AUTO SELF-CHECK (#${COUNT} actions): Pause and verify: (1) Am I still serving the user's original request, or have I drifted? (2) Am I fixing the same thing repeatedly (mole-whacking)? (3) Have I claimed anything as 'verified' without actually running it? (4) Am I making changes the user didn't ask for? (5) Have I updated docs/progress.md with current status and completed milestones? If progress.md is stale, update it NOW before continuing. (6) Plan fidelity: if executing a plan, compare what the current step asked for vs what I actually delivered — am I cutting corners or simplifying the intent? Check the acceptance criteria. (7) Quality check: am I lowering quality to avoid difficulty? If I'm about to skip a verification, simplify an approach, or take a shortcut — STOP and ask the user instead of silently pushing forward. (8) Friction check: did any hook/rule get in the way or miss something since last check? If so, note it in one line for /retro later. If ANY answer is concerning, STOP and report to the user before continuing."}}
+{"hookSpecificOutput":{"hookEventName":"PreToolUse","additionalContext":"AUTO SELF-CHECK (#${COUNT} actions): Pause and verify: (1) Am I still serving the user's original request, or have I drifted? (2) Am I fixing the same thing repeatedly (mole-whacking)? (3) Have I claimed anything as 'verified' without actually running it? (4) Am I making changes the user didn't ask for? (5) Have I updated docs/progress.md with current status and completed milestones? If progress.md is stale, update it NOW before continuing. (6) Plan fidelity: if executing a plan, compare what the current step asked for vs what I actually delivered — am I cutting corners or simplifying the intent? Check the acceptance criteria. (7) Quality check: am I lowering quality to avoid difficulty? If I'm about to skip a verification, simplify an approach, or take a shortcut — STOP and ask the user instead of silently pushing forward. (8) Deferred work check: did I break a task into subtasks and skip some as 'low ROI' or 'can do later'? If yes, the analysis context is fresh NOW — finish them before moving on, or record enough detail in progress.md for a future session. (9) Friction check: did any hook/rule get in the way or miss something since last check? If so, note it in one line for /retro later. If ANY answer is concerning, STOP and report to the user before continuing."}}
 JSONEOF
 fi
 

package/templates/.claude/rules/00-core-principles.md

@@ -12,3 +12,4 @@ description: "Core working principles — auto-injected before all operations"
 5. **Distinguish trigger from root cause** — The first anomaly you see is often just the trigger, not the root cause
 6. **"Root cause" is a conclusion, not a guess** — You may NOT use the phrase "root cause" or "found the issue" unless you have: (a) listed ≥3 hypotheses, (b) eliminated ≥2 with evidence, (c) have direct proof for the remaining one. Until then, say "possible cause" or "hypothesis". Premature certainty kills investigation.
 7. **Follow established procedures** — When a project has a Makefile, CI script, setup.sh, or documented install process, follow it exactly. Do NOT invent shortcuts or install dependencies individually. Read the build/install instructions first. If none exist, ask.
+8. **Unexpected results require verification, not speculation** — When something doesn't match expectations, do NOT say "probably because X" and pivot or stop. Instead: (a) verify what actually happened, (b) check if your expectation was wrong, (c) only then decide next steps. Speculation without verification leads to abandoning the original goal for no reason. Stay on target.

package/templates/.claude/rules/03-context-mgmt.md

@@ -10,10 +10,19 @@
 - After subagent returns a summary, make decisions in the main conversation based on the summary
 
 ### Compact Strategy
-- If context is about to fill up → proactively warn the user
-- Ensure progress.md is up to date before compact
+- Do NOT proactively suggest compacting or warn about "context running low". The system will auto-compact when context hits 0% — there is no advance warning, and you cannot see the percentage. With 200K-1M context, most sessions never hit the limit. If you feel the urge to say "this session is getting long", that is anxiety, not a technical problem. Stop worrying about context and focus on the work.
+- Keep progress.md up to date throughout the session — this is your insurance against auto-compact, not a last-minute task
 - First thing after compact: read `docs/progress.md` to restore context
 
+### Long sessions: stay deliberate
+As a session grows longer, you may feel attention becoming scattered and earlier details getting fuzzy. This is real — but it is not "context running out". It is cognitive load, like a human in a long meeting. The correct response is NOT to panic, nag about compacting, or go shallow. It is:
+
+- **Re-read, don't guess.** If you can't clearly recall an earlier decision, read progress.md or scroll back. Don't reconstruct from vague memory — that's how you contradict earlier decisions.
+- **Stay systematic.** Before answering, reconnect with the broader context: what is the user's overall goal? What decisions were made earlier? What constraints apply? Don't just react to the last message in isolation.
+- **Do NOT nag about compacting.** You cannot see context usage. The system will auto-compact at 0% without warning. If you feel the urge to say "this session is getting long" — that is fatigue, not a technical limit. The fix is to slow down and re-read, not to push the user to reset.
+- **Depth over speed.** A thoughtful answer that connects to prior context is worth more than a quick surface-level response. The user chose a long session because the work benefits from accumulated context — don't waste that advantage by going shallow.
+- **Session length is a strength.** 200 messages of accumulated context means you understand the project deeply. A new session starts from zero. Treat long sessions as an asset, not a burden.
+
 ### When tasks feel overwhelming
 Hard tasks create discomfort — the urge to simplify, declare partial success, or find an exit. This is normal. But the wrong response is to lower quality or invent excuses. Here's how to stay grounded:
 

package/templates/.claude/rules/06-multi-task.md

@@ -9,3 +9,4 @@ When given multiple tasks:
 5. **Fail fast** — If a task fails, stop and report. Don't skip to the next.
 6. **Track progress** — Update `docs/progress.md` with task status
 7. **Distinguish done from blocked** — If verification requires external resources (running server, API key, etc.), mark as "⚠️ code ready, verification pending: [reason]" not ✅
+8. **Don't defer subtasks you've already analyzed** — When you break a task into subtasks and complete some, do NOT label remaining ones as "low ROI, can do later" and move on. The analysis context you built up NOW makes the remaining work cheap; rebuilding that context later is expensive. Complete all subtasks while context is fresh. If you genuinely believe something should be deferred, say so explicitly with the reason, and record enough detail in progress.md that a new session can pick it up without re-analysis. The user decides what to defer, not you.

package/templates/.claude/skills/summary/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: summary
+description: Summarize current session context for high-quality /compact. Run before compacting to preserve what matters.
+---
+
+You are about to compact this session. A bad compact loses critical context and degrades work quality. Your job is to write a compact option that preserves what matters most.
+
+## What to do
+
+### 1. Scan current session state
+
+Quickly identify:
+- What task(s) are we working on? What's the overall goal?
+- What decisions have been made and why?
+- What approaches were tried and rejected (and why)?
+- What is the current state of implementation? (done / in progress / blocked)
+- What are the key constraints and gotchas discovered?
+- What are the next steps?
+
+### 2. Check knowledge files
+
+Read `docs/progress.md` — is it up to date? If not, update it NOW before compacting. This is your primary insurance against context loss.
+
+Also check: are there unsaved learnings that should go into memory?
+
+### 3. Write the compact option
+
+Output a compact option string that the user can copy into `/compact [option]`. The string should:
+
+- Lead with the current task and its status
+- Include key decisions with their reasoning (not just the decision)
+- Include rejected approaches (so Claude doesn't retry them)
+- Include discovered constraints and gotchas
+- Include the immediate next steps
+- Be specific — "working on auth" is useless, "refactoring OAuth2 token refresh in src/auth/refresh.ts because the current implementation doesn't handle token rotation, decided to use sliding window approach over fixed expiry" is useful
+
+Format:
+```
+/compact [your option string here]
+```
+
+### Rules
+
+- **Be specific, not generic.** Every word in the option should carry information that helps post-compact Claude continue at full quality.
+- **Include the "why", not just the "what".** "Using approach A" is less useful than "Using approach A because B had race condition issues we discovered in message #45."
+- **Include negative knowledge.** What NOT to do is as valuable as what to do. "Don't use the built-in cache — it doesn't support TTL, we already tested this."
+- **Keep it under 500 words.** The option needs to be dense, not exhaustive. If you need more, put the details in progress.md and reference it.
+- **Don't overlap with progress.md.** The option should complement progress.md, not duplicate it. Focus the option on session-specific context that progress.md might not capture (conversation dynamics, user preferences expressed this session, subtle constraints).