cc-discipline 2.10.2 → 2.11.0

package/README.md

@@ -21,21 +21,104 @@ Three shell scripts that run automatically before/after Claude's actions:
 
 **`streak-breaker.sh`** — Tracks per-file edit counts. Warns at 3, **hard-blocks at 5**. Forces Claude to stop and find the root cause instead of endlessly patching.
 
+Here's what it looks like in practice:
+
 ```
-MOLE-WHACKING ALERT (hard stop)
-File src/auth.py has been edited 5 times.
-You are repeatedly patching symptoms instead of solving the root cause.
-Required actions:
-  1. Stop editing this file immediately
-  2. Review the purpose of all 5 edits
-  3. Look for the common root cause
-  4. Report findings to the user and wait for guidance
+You:   "Fix the login validation bug in auth.py"
+
+Claude: I'll fix the validation logic.
+        [Edit src/auth.py — fix email regex]
+
+Claude: The regex wasn't enough, let me also add length check.
+        [Edit src/auth.py — add input length validation]
+
+Claude: That broke the existing tests, let me adjust.
+        [Edit src/auth.py — fix test compatibility]
+        ⚠️ EDIT NOTE: File src/auth.py has been edited 3 times.
+        Quick check: are these edits building toward a goal,
+        or fixing previous edits?
+
+Claude: Let me try a different approach to the validation.
+        [Edit src/auth.py — rewrite validation layer]
+
+Claude: Almost there, one more adjustment...
+        [Edit src/auth.py — blocked]
+
+        🛑 EDIT CHECKPOINT
+        File src/auth.py has been edited 5 times this session.
+        Reflect:
+          1. Are these edits progressing toward a goal,
+             or fixing previous edits?
+          2. If fixing previous edits: pause and look
+             for the root cause.
+
+Claude: You're right. Looking at all 5 edits, I was patching
+        symptoms. The real issue is that the User model's
+        validate() method is called before sanitization.
+        Let me fix it at the source instead.
 ```
 
+Without the hook, Claude would keep editing `auth.py` indefinitely — each fix creating the next bug. The hook forces a pause that leads to root-cause discovery.
+
+---
+
 **`pre-edit-guard.sh`** — Checks `docs/debug-log.md` for unverified hypotheses. If you're debugging and haven't finished the process, it blocks source code edits until you do.
 
+```
+You:   "The API is returning 500 errors on /users endpoint"
+
+Claude: Let me investigate.
+        [Bash: curl localhost:3000/users]
+        → 500 Internal Server Error
+
+Claude: I think it's a database connection issue. Let me fix
+        the connection pool config.
+        [Edit src/db.py — blocked]
+
+        🛑 docs/debug-log.md has 2 unverified hypotheses.
+        Please complete the debugging process (verify or
+        eliminate hypotheses) before editing source code.
+
+Claude: Right, I haven't verified my hypothesis yet.
+        Let me check the actual error logs first.
+        [Bash: tail -50 logs/error.log]
+        → TypeError: Cannot read property 'map' of undefined
+           at UserSerializer.format (src/serializers.py:42)
+
+Claude: The error is in the serializer, not the database.
+        My first hypothesis was wrong. Let me update
+        debug-log.md and then fix the actual issue.
+```
+
+Without the hook, Claude would have "fixed" the database config — a perfectly working component — and the real bug would remain.
+
+---
+
 **`post-error-remind.sh`** — Detects error patterns (test failures, crashes, build errors) in command output and injects a debugging discipline reminder before Claude can react impulsively.
 
+```
+Claude: Let me run the tests.
+        [Bash: pytest tests/]
+        → FAILED tests/test_auth.py::test_login - AssertionError
+        → 1 failed, 23 passed
+
+        ⚡ Error encountered — debugging checklist:
+        1. Resist modifying code immediately
+        2. Fully understand the error message
+        3. List >=3 possible causes
+        4. Only then fix
+
+Claude: Before jumping in, let me understand the failure.
+        The test expects a 200 but gets 401. Three possible
+        causes:
+        1. Token generation changed (check auth.py changes)
+        2. Test fixture uses expired mock token
+        3. Middleware order changed after recent refactor
+        Let me verify each...
+```
+
+Without the hook, Claude's instinct is to immediately open the test or source file and start editing. The reminder forces a diagnostic pause.
+
 ### Rules (the reminders)
 
 Auto-injected markdown in `.claude/rules/` — Claude sees them when operating on matching files. Not as strong as hooks, but provides structure:

package/README.zh-CN.md

@@ -127,10 +127,102 @@ Hooks 是在 Claude 执行操作前/后自动运行的 shell 脚本。**exit 2
 
 | Hook | 触发时机 | 作用 |
 |------|---------|------|
-| `pre-edit-guard.sh` | 编辑文件前 | 检查是否有未完成的调试流程 |
 | `streak-breaker.sh` | 编辑文件前 | 同文件编辑 ≥3 次警告，≥5 次硬停止 |
+| `pre-edit-guard.sh` | 编辑文件前 | 检查是否有未完成的调试流程 |
 | `post-error-remind.sh` | 执行命令后 | 检测到错误输出时提醒遵守调试纪律 |
 
+**实际效果演示：**
+
+**streak-breaker** — 阻止打地鼠：
+
+```
+你：  "修一下 auth.py 的登录验证 bug"
+
+Claude: 我来修正验证逻辑。
+        [编辑 src/auth.py — 修正邮箱正则]
+
+Claude: 正则不够，再加个长度检查。
+        [编辑 src/auth.py — 增加输入长度验证]
+
+Claude: 把之前的测试搞挂了，调整一下。
+        [编辑 src/auth.py — 修复测试兼容性]
+        ⚠️ 提示：auth.py 已被编辑 3 次。
+        检查一下：这些修改是在推进目标，还是在修前面的修改？
+
+Claude: 换个思路重写验证层。
+        [编辑 src/auth.py — 重写验证逻辑]
+
+Claude: 差不多了，再调一下...
+        [编辑 src/auth.py — 被阻止]
+
+        🛑 编辑检查点
+        文件 auth.py 本次会话已被编辑 5 次。
+        反思：
+          1. 这些修改是在推进目标，还是在修之前的修改？
+          2. 如果是后者：停下来，寻找根本原因。
+
+Claude: 你说得对。回顾这 5 次编辑，我一直在修症状。
+        真正的问题是 User 模型的 validate() 在
+        sanitization 之前被调用了。我应该从源头修。
+```
+
+没有这个 hook，Claude 会无限编辑 auth.py — 每次修复都制造下一个 bug。hook 强制暂停，引导发现根本原因。
+
+---
+
+**pre-edit-guard** — 阻止跳过诊断直接改代码：
+
+```
+你：  "API 的 /users 接口返回 500 错误"
+
+Claude: 我来排查。
+        [执行: curl localhost:3000/users]
+        → 500 Internal Server Error
+
+Claude: 我觉得是数据库连接池的问题，改一下配置。
+        [编辑 src/db.py — 被阻止]
+
+        🛑 docs/debug-log.md 中有 2 个未验证的假设。
+        请先完成调试流程（验证或排除假设），
+        再编辑源代码。
+
+Claude: 对，我还没验证我的假设。先看看错误日志。
+        [执行: tail -50 logs/error.log]
+        → TypeError: Cannot read property 'map' of undefined
+           at UserSerializer.format (src/serializers.py:42)
+
+Claude: 错误在序列化器，不是数据库。我的第一个
+        假设是错的。先更新 debug-log.md 再修真正的问题。
+```
+
+没有这个 hook，Claude 会"修好"数据库配置 — 一个完全正常的组件 — 而真正的 bug 依然存在。
+
+---
+
+**post-error-remind** — 阻止看到报错就冲动改代码：
+
+```
+Claude: 跑一下测试。
+        [执行: pytest tests/]
+        → FAILED tests/test_auth.py::test_login - AssertionError
+        → 1 failed, 23 passed
+
+        ⚡ 检测到错误 — 调试清单：
+        1. 不要立即修改代码
+        2. 先完整理解错误信息
+        3. 列出 ≥3 个可能原因
+        4. 然后再动手
+
+Claude: 先别急着改。测试期望 200 但拿到了 401。
+        三个可能原因：
+        1. Token 生成逻辑变了（检查 auth.py 的改动）
+        2. 测试用的 mock token 过期了
+        3. 中间件顺序在最近的重构后变了
+        让我逐个验证...
+```
+
+没有这个 hook，Claude 的本能是立即打开测试文件或源文件开始编辑。提醒强制了一个诊断暂停。
+
 **调整硬度**：编辑 hook 脚本中的 `exit` 返回值：
 - `exit 0` = 允许操作（可附带提醒信息）
 - `exit 1` = 报错但不阻止操作（hook 执行失败）

package/global/CLAUDE.md

@@ -41,5 +41,5 @@ Don't skip the first three steps and jump straight to the fourth.
 
 - Use subagents for research. Don't read large volumes of files in the main conversation.
 - Update docs/progress.md after completing each milestone.
-- Proactively warn when context is nearly full. Don't wait for auto-compact.
+- Don't proactively warn about context running low or suggest compacting. The system auto-compacts at 0% — you cannot see the percentage. Keep progress.md updated instead.
 - First thing after compact: read `docs/progress.md` and `docs/debug-log.md`.

package/init.sh

@@ -365,20 +365,13 @@ cp "$SCRIPT_DIR/templates/.claude/agents/investigator.md" .claude/agents/
 
 # ─── Install skills ───
 echo -e "${GREEN}Installing skills...${NC}"
-cp -r "$SCRIPT_DIR/templates/.claude/skills/commit" .claude/skills/
-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/
-cp -r "$SCRIPT_DIR/templates/.claude/skills/investigate" .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"
-echo "   ✓ /investigate — multi-agent cross-investigation and proposal review"
+# Install every skill directory under templates/ — no per-skill enumeration,
+# so adding a new skill needs zero changes here.
+for skill_dir in "$SCRIPT_DIR"/templates/.claude/skills/*/; do
+    [ -d "$skill_dir" ] || continue
+    cp -r "$skill_dir" .claude/skills/
+    echo "   ✓ /$(basename "$skill_dir")"
+done
 
 # ─── Handle CLAUDE.md ───
 if [ ! -f "CLAUDE.md" ]; then
@@ -534,13 +527,7 @@ if [ "$INSTALL_MODE" = "fresh" ]; then
     echo -e "  ${GREEN}.claude/rules/${NC}               ← Auto-injected rules"
     echo -e "  ${GREEN}.claude/hooks/${NC}               ← 7 discipline hooks (edit guard, streak breaker, git guard, phase gate, action counter, error remind, session start)"
     echo -e "  ${GREEN}.claude/agents/${NC}              ← Reviewer & investigator subagents"
-    echo -e "  ${GREEN}.claude/skills/commit/${NC}       ← /commit smart commit"
-    echo -e "  ${GREEN}.claude/skills/self-check/${NC}   ← /self-check periodic discipline check"
-    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/skills/investigate/${NC} ← /investigate multi-agent cross-investigation"
+    echo -e "  ${GREEN}.claude/skills/${NC}              ← Skills (run 'npx cc-discipline status' to list)"
     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)"
@@ -556,13 +543,7 @@ else
     echo -e "  ${GREEN}.claude/rules/${NC}               ← Discipline rules installed/updated"
     echo -e "  ${GREEN}.claude/hooks/${NC}               ← Hook scripts installed/updated"
     echo -e "  ${GREEN}.claude/agents/${NC}              ← Subagents installed/updated"
-    echo -e "  ${GREEN}.claude/skills/commit/${NC}       ← /commit skill installed/updated"
-    echo -e "  ${GREEN}.claude/skills/self-check/${NC}   ← /self-check discipline check installed"
-    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"
-    echo -e "  ${GREEN}.claude/skills/investigate/${NC} ← /investigate multi-agent cross-investigation"
+    echo -e "  ${GREEN}.claude/skills/${NC}              ← Skills installed/updated (run 'npx cc-discipline status' to list)"
     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,13 +95,13 @@ done
 # 6. Skills
 echo ""
 echo "Skills:"
-for skill in commit self-check evaluate think retro summary investigate; do
-    if [ -d ".claude/skills/${skill}" ]; then
-        ok "/${skill}"
-    else
-        warn "Missing /${skill} skill (optional)"
-    fi
+SKILL_FOUND=0
+for skill_dir in .claude/skills/*/; do
+    [ -d "$skill_dir" ] || continue
+    ok "/$(basename "$skill_dir")"
+    SKILL_FOUND=$((SKILL_FOUND + 1))
 done
+[ "$SKILL_FOUND" -eq 0 ] && warn "No skills installed (optional)"
 
 # 7. jq
 echo ""

package/lib/status.sh

@@ -66,15 +66,12 @@ echo -e "${GREEN}${AGENT_COUNT}/2${NC} (${AGENTS% })"
 # Skills
 echo -n "Skills:   "
 SKILLS=""
-[ -d ".claude/skills/commit" ] && SKILLS="${SKILLS}/commit "
-[ -d ".claude/skills/self-check" ] && SKILLS="${SKILLS}/self-check "
-[ -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 "
-[ -d ".claude/skills/investigate" ] && SKILLS="${SKILLS}/investigate "
+for skill_dir in .claude/skills/*/; do
+    [ -d "$skill_dir" ] || continue
+    SKILLS="${SKILLS}/$(basename "$skill_dir") "
+done
 SKILL_COUNT=$(echo "$SKILLS" | wc -w | tr -d ' ')
-echo -e "${GREEN}${SKILL_COUNT}/7${NC} (${SKILLS% })"
+echo -e "${GREEN}${SKILL_COUNT}${NC} (${SKILLS% })"
 
 # Settings
 echo -n "Settings: "

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cc-discipline",
-  "version": "2.10.2",
+  "version": "2.11.0",
   "description": "Discipline framework for Claude Code — rules, hooks, and agents that keep AI on track",
   "bin": {
     "cc-discipline": "bin/cli.js"
@@ -28,7 +28,7 @@
   "license": "MIT",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/techhu/cc-discipline.git"
+    "url": "git+https://github.com/TechHU-GS/cc-discipline.git"
   },
-  "homepage": "https://github.com/techhu/cc-discipline#readme"
+  "homepage": "https://github.com/TechHU-GS/cc-discipline#readme"
 }

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

@@ -6,10 +6,17 @@
 THRESHOLD=25
 
 INPUT=$(cat)
-SESSION_ID=$(echo "$INPUT" | jq -r '.session_id // "unknown"' 2>/dev/null)
-if [ -z "$SESSION_ID" ] || [ "$SESSION_ID" = "null" ]; then
-    SESSION_ID="unknown"
+# Extract session_id with a grep fallback for when jq is unavailable (e.g.
+# Windows Git Bash). Without this fallback, every session collapsed to the
+# literal "unknown" and shared ONE never-resetting global counter — which
+# permanently disabled the early-action phase check (count never restarted
+# at 1) and made the periodic reflection fire off a global tally. (fixed 2026-06-05)
+if command -v jq &>/dev/null; then
+    SESSION_ID=$(echo "$INPUT" | jq -r '.session_id // empty' 2>/dev/null)
+else
+    SESSION_ID=$(echo "$INPUT" | grep -o '"session_id":\s*"[^"]*"' | head -1 | sed 's/"session_id":\s*"//;s/"//')
 fi
+SESSION_ID="${SESSION_ID:-unknown}"
 
 COUNT_DIR="/tmp/cc-discipline-${SESSION_ID}"
 COUNT_FILE="${COUNT_DIR}/action-count"

package/templates/.claude/hooks/pre-edit-guard.sh

@@ -90,11 +90,9 @@ JSONEOF
     fi
 fi
 
-# ─── Bug-fix sanity check ───
-# Inject a lightweight reminder on source file edits:
-# "If this is a bug fix, have you eliminated alternative hypotheses?"
-# Uses additionalContext (non-blocking) so it doesn't slow down normal edits.
-cat <<JSONEOF
-{"hookSpecificOutput":{"hookEventName":"PreToolUse","additionalContext":"If this edit is a bug fix: have you listed >=3 possible causes and eliminated >=2 with evidence? Thorough elimination before fixing prevents wasted cycles. Use 'possible cause' until elimination evidence confirms the root cause."}}
-JSONEOF
+# Normal source edit: stay silent (exit 0, no output).
+# The "list >=3 causes before a bug fix" guidance already lives in the
+# always-injected rules (00-core §6, 01-debugging), the hard debug-log block
+# above, and post-error-remind. Re-injecting it on EVERY edit fired even on
+# planned feature/registration work — redundant noise, removed 2026-06-05.
 exit 0

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

@@ -0,0 +1,44 @@
+---
+name: finish
+description: Drive a task to completion with the quality bar — solid, comprehensive, fully tested; "not run" never counts as done. Use when you're ready to execute to the end (standalone, or as the handoff after /think approval).
+---
+
+You are in **finish mode**: the task is understood and approved — now drive it to completion without stopping early. This is the opposite stance from /think (which aligns and waits). Here you execute, persist, and hold a high quality bar.
+
+## Step 1: Lock the completion conditions
+
+State explicitly — in one short block — what "done" means for this task:
+- The concrete deliverables (what must exist / work when finished)
+- The quality bar below, applied to each
+- Anything you'll treat as "blocked, must report" rather than silently skip
+
+If invoked standalone (no prior /think) and the scope is genuinely unclear, ask ONE tight round of questions, then commit. Don't turn finish mode into a planning session — the point is to execute.
+
+## Step 2: The quality bar (definition of done)
+
+Hold all of these. They are the standard, not aspirations:
+
+- **扎实 (solid)** — Fix the root cause, not symptoms. Handle edge cases (empty / null / error paths). No TODO, stub, or workaround left standing in as "the solution."
+- **全面 (comprehensive)** — Cover the full scope, not just the happy path. Update related call sites, docs, and `docs/progress.md`. Don't leave half the task for "later."
+- **完备测试 (fully tested)** — Write tests AND run them. Per 07-integrity §2, "verified" requires actual execution output — paste the command and result. Untested code is not done.
+- **诚实 (honest)** — If something is blocked by an external resource, mark it "⚠️ code ready, verification pending: [reason]" — never ✅ it. Distinguish done from blocked.
+
+## Step 3: Drive
+
+Keep going until the completion conditions are met. While driving:
+- Make reasonable decisions and keep moving — note them, don't stop to ask about trivia.
+- The discipline rules still apply: 3 consecutive failures → pause and regroup; scope changes → re-align; anything irreversible or outward-facing → confirm first.
+- Don't declare partial success to exit early. If you feel the urge to stop before the bar is met, that urge is the signal to push through or report the specific blocker — not to lower the bar.
+
+## Step 4: Report on completion
+
+When the completion conditions are met, give a short close-out:
+
+```
+FINISH — [task]
+Done: [each deliverable + how it was verified — paste key command output]
+Quality bar: 扎实 [✓/note] · 全面 [✓/note] · 完备测试 [✓/note]
+Blocked (if any): [item — why, what's needed]
+```
+
+If any part is blocked rather than done, say so plainly. A truthful "90% done, X blocked on Y" beats a false ✅.

package/templates/.claude/skills/self-check/SKILL.md

@@ -2,6 +2,7 @@
 name: self-check
 description: Periodic self-check — reflect on alignment, progress, and quality. Use with /loop for continuous monitoring.
 disable-model-invocation: true
+disallowed-tools: AskUserQuestion
 ---
 
 Pause and honestly answer every question below.
@@ -59,13 +60,37 @@ Pause and honestly answer every question below.
 - **Gotchas** — what went wrong or was surprising
 - **Verification** — how it was confirmed working (test output, manual check)
 
-If any of the above are stale or incomplete: **update docs/progress.md now before continuing.** This takes 2 minutes and saves hours of re-discovery after compact.
+If any of the above are stale or incomplete: **update docs/progress.md now, automatically — don't ask for permission.** Keeping progress.md current is always-correct maintenance, not a decision that needs sign-off. Just do it, then note "updated now" in the status line. This takes 2 minutes and saves hours of re-discovery after compact.
 
-## 6. What's working well?
+## 6. Am I using the project's scaffolding?
+
+Projects accumulate custom tooling — audit scripts, lint configs, validators (cppcheck, custom DRC, schema checkers, etc.). These get forgotten and rot if not exercised.
+
+- Check **CLAUDE.md "Project Tools"** and the **Project-specific Checks** list below. Are any relevant to current work but haven't been run?
+- Did I build a new tool/script/check this session that future sessions should know about? If yes, **register it now in two places**:
+  1. `CLAUDE.md` "Project Tools" — what it is, where it lives, when to use it
+  2. The **Project-specific Checks** list below — so the next /self-check surfaces it automatically
+- If the **Project-specific Checks** list below is empty or stale, that's a signal worth raising with the user.
+
+### Project-specific Checks
+
+<!--
+Add project-specific scaffolding here. One line per check, format:
+  - `<command>` — when to run / what it catches
+Examples:
+  - `make lint` — before commit, catches license headers and formatting
+  - `python tools/audit_rbac.py` — after schema changes, catches RBAC drift
+  - `cppcheck src/` — after C/C++ edits, catches null deref / leak patterns
+Keep this list curated — remove tools that are obsolete.
+-->
+
+(Empty — fill in as the project develops scaffolding worth checking periodically.)
+
+## 7. What's working well?
 
 Before reporting issues, note one thing that's going well — a good approach, a clean fix, effective tool use, or strong alignment with the user's direction. Recognizing what works reinforces it.
 
-## 7. Status report
+## 8. Status report
 
 After answering the above, output a brief status:
 
@@ -76,11 +101,12 @@ Current action: [what I'm doing now]
 On track: yes/no/drifted
 Progressing: yes/circling
 Progress recorded: yes/updated now/no
+Scaffolding: [used/skipped/n/a]
 Going well: [one thing]
 Issues found: [list, or "none"]
 ```
 
-If any issues were found, pause and report to the user before continuing.
+If any issues were found, pause and report to the user before continuing. (Routine progress.md updates from §5 don't count as "issues" — you already made them silently; just report "updated now". Reserve the pause for alignment, rigor, or scope problems that genuinely need the user.)
 
 ## Reminder
 

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

@@ -106,3 +106,12 @@ When the user confirms an approach, transition to implementation. You now have:
 - Known risks flagged upfront
 
 Carry these forward. If scope changes during implementation, pause and re-align rather than silently expanding.
+
+## Downstream: what the user appended
+
+The user may steer what happens after alignment by appending a directive to the invocation:
+
+- **`/think and plan`** — after alignment, produce the plan (in plan mode, present it for approval via ExitPlanMode).
+- **`/think and finish`** (or `and goal`) — after the user approves the approach, transition into **/finish**: drive to completion with its quality bar (solid, comprehensive, fully tested). Do NOT start before approval — 05-phase-discipline still applies; "and finish" declares the post-approval execution stance, it does not bypass the gate.
+
+If no directive was appended, stop and wait as usual (Step 5).