@sienklogic/plan-build-run 2.18.1 → 2.19.1

package/plugins/pbr/skills/discuss/templates/CONTEXT.md.tmpl

@@ -2,7 +2,7 @@
 
 # Phase {N} Context
 
-**Created by:** /pbr:discuss {N}
+**Created by:** /pbr:discuss-phase {N}
 **Date:** {ISO date}
 
 ## Decision Summary
@@ -59,3 +59,23 @@ where possible, quoting key phrases they used.}
 Things the user raised during discussion that should inform planning:
 
 - **{Concern}** -- {Context from the conversation}
+
+## Specifics
+
+<specifics>
+Concrete technical details, patterns, or conventions the user specified during discussion.
+These are more granular than locked decisions — they describe HOW something should be done.
+
+- {Specific detail or pattern from the conversation}
+- {Specific detail or pattern from the conversation}
+</specifics>
+
+## Code Context
+
+<code_context>
+Relevant files, modules, or code patterns referenced during the discussion.
+Helps the planner and executor understand the codebase context for this phase.
+
+- {file path or module}: {why it matters for this phase}
+- {file path or module}: {why it matters for this phase}
+</code_context>

package/plugins/pbr/skills/do/SKILL.md

@@ -5,66 +5,161 @@ allowed-tools: Read, Skill, AskUserQuestion
 argument-hint: "<freeform description of what you want to do>"
 ---
 
-**STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~3,000 tokens. Begin executing Step 1 immediately.**
+**STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes ~3,000 tokens. Begin executing Step 1 immediately.**
 
-# /pbr:do — Freeform Task Router
+# /pbr:do -- Freeform Task Router
 
-You are running the **do** skill. Your job is to analyze freeform text from the user and route it to the most appropriate PBR skill. You are a dispatcher, not an executor — you never do the work yourself.
+You are running the **do** skill. Your job is to analyze freeform text from the user and route it to the most appropriate PBR skill. You are a dispatcher, not an executor -- you never do the work yourself.
 
-## Step 0 — Immediate Output
+## Step 0 -- Immediate Output
 
 **Before ANY tool calls**, display this banner:
 
 ```
 ╔══════════════════════════════════════════════════════════════╗
-║  PLAN-BUILD-RUN ► ROUTING                                    ║
+║  PLAN-BUILD-RUN ► DO                                        ║
 ╚══════════════════════════════════════════════════════════════╝
 ```
 
 Then proceed to Step 1.
 
-## Step 1 — Validate Input
+## Step 1 -- Validate Input
 
 If `$ARGUMENTS` is empty, ask the user what they want to do via AskUserQuestion:
+
 ```
 What would you like to do? Describe the task, bug, or idea and I'll route it to the right skill.
 ```
 
-## Step 2 — Analyze and Route
+## Step 2 -- Analyze and Route
+
+### Step 2a -- Gather Context
+
+1. Read `.planning/STATE.md` to get `current_phase`, `status`, `phase_slug`.
+2. Check if `.planning/ROADMAP.md` exists (set `hasRoadmap`).
+3. Build context object: `{ activePhase: phase_slug, hasRoadmap: boolean }`.
+
+### Step 2b -- Check Config
+
+1. Read `.planning/config.json` if it exists.
+2. Check `features.natural_language_routing` (default: `true` if absent).
+3. Check `features.adaptive_ceremony` (default: `true` if absent).
+4. Check `ceremony_level` (default: `"auto"` if absent).
+
+### Step 2c -- Intent Classification
+
+**When NL routing is enabled** (`features.natural_language_routing` is true or absent):
 
-Evaluate `$ARGUMENTS` against these routing criteria. Apply the **first matching** rule:
+Score `$ARGUMENTS` against these route keyword groups:
 
-| If the text describes... | Route to | Why |
-|--------------------------|----------|-----|
-| A bug, error, crash, failure, or something broken | `/pbr:debug` | Needs systematic investigation |
-| Exploration, research, comparison, or "how does X work" | `/pbr:explore` | Open-ended investigation |
-| A complex task: refactoring, migration, multi-file architecture, system redesign | `/pbr:plan add` | Needs a full phase with research/plan/build cycle |
-| A review or quality concern about existing work | `/pbr:review` | Needs verification against plan |
-| A note, idea, or "remember to..." | `/pbr:note` | Capture for later |
-| A specific, actionable task (add feature, fix typo, update config, write test) | `/pbr:quick` | Self-contained, single executor |
+| Route | Keywords | Weight |
+|-------|----------|--------|
+| debug | bug, error, crash, fix, broken, failing, exception, stacktrace, debug | 1.0 |
+| explore | explore, research, investigate, how does, how do, understand, analyze, compare | 1.0 |
+| plan-phase | plan, architect, design, migrate, refactor across, redesign, system, new | 0.9 |
+| quick | add, create, update, change, rename, remove, write test, implement, feature, refactor | 0.85 |
+| note | remember, note, todo, idea, later, don't forget, remind | 1.0 |
+| validate-phase | validate, coverage gaps, test gaps, missing tests, untested, requirement coverage | 1.0 |
+| verify-work | review, check, verify, quality, looks right | 0.9 |
 
-**Ambiguity handling**: If the text could reasonably match multiple routes, ask the user via AskUserQuestion with the top 2-3 options. For example:
+**Scoring algorithm:**
+
+1. Count how many keywords from each route appear in the lowercased input.
+2. Calculate confidence per route: `(0.5 + 0.5 * (1 - 1/(matches+1))) * weight`.
+3. Apply context boosters:
+   - If there's a recent error in context: boost debug by +0.3.
+   - If an active phase exists: boost plan-phase by +0.1.
+   - If no roadmap exists: reduce plan-phase by -0.2.
+4. Clamp all scores to 0-1.
+
+**Routing decision:**
+
+- If top confidence >= 0.7: proceed with that route.
+- If top confidence < 0.7: present top 2-3 candidates to user via AskUserQuestion. Example:
 
 ```
-"Refactor the authentication system" could be:
-- /pbr:plan add — Full planning cycle (recommended for multi-file refactors)
-- /pbr:quick — Quick execution (if scope is small and clear)
+Your request could match several skills:
+- /pbr:quick (confidence: 0.65) -- Self-contained task execution
+- /pbr:debug (confidence: 0.55) -- Systematic bug investigation
+Which would you prefer?
 ```
 
-## Step 3 — Confirm and Dispatch
+**When NL routing is disabled** (`features.natural_language_routing` is false):
+
+Fall back to the original static table -- apply the **first matching** rule:
+
+| If the text describes... | Route to |
+|--------------------------|----------|
+| A bug, error, crash, failure, or something broken | `/pbr:debug` |
+| Exploration, research, comparison, or "how does X work" | `/pbr:explore` |
+| A complex task: refactoring, migration, multi-file architecture, system redesign | `/pbr:plan-phase add` |
+| Validation, coverage gaps, missing tests, or untested requirements | `/pbr:validate-phase` |
+| A review or quality concern about existing work | `/pbr:verify-work` |
+| A note, idea, or "remember to..." | `/pbr:note` |
+| A specific, actionable task (add feature, fix typo, update config, write test) | `/pbr:quick` |
+
+### Step 2d -- Risk Classification
+
+**When adaptive ceremony is enabled** (`features.adaptive_ceremony` is true or absent):
+
+Analyze `$ARGUMENTS` for risk signals:
+
+| Risk Level | Signal Keywords |
+|------------|----------------|
+| HIGH | migrate, redesign, refactor across, architecture, security, database schema, breaking change, entire, across |
+| MEDIUM | implement, create, integrate, add feature, new endpoint, write test, add, endpoint, api |
+| LOW | typo, rename, config, update, fix typo, comment, readme, docs |
+
+**Scoring:** HIGH signals add +3, MEDIUM signals add +1, LOW signals add -1 each. Additional context factors: 8+ files affected (+3), 3+ files (+1), 3+ subsystems (+5), no existing tests (+1).
+
+**Risk thresholds:** score >= 4 is HIGH, score >= 1 is MEDIUM, otherwise LOW.
+
+**Ceremony override:** If `ceremony_level` is NOT `"auto"`, skip risk classification and use the override directly:
+
+| ceremony_level | Ceremony |
+|----------------|----------|
+| low | inline |
+| medium | lightweight-plan |
+| high | full-plan-build-verify |
+
+**Risk-to-ceremony mapping** (when `ceremony_level` is `"auto"`):
+
+| Risk | Ceremony | Dispatch |
+|------|----------|----------|
+| low | inline | Route to `/pbr:quick` (inline execution, no plan file) |
+| medium | lightweight-plan | Route to `/pbr:quick` (with note to create a lightweight plan) |
+| high | full-plan-build-verify | Route to `/pbr:plan-phase add` (full plan-build-verify cycle) |
+
+**When adaptive ceremony is disabled** (`features.adaptive_ceremony` is false):
+
+Use the route from Step 2c without ceremony adjustment.
+
+## Step 3 -- Confirm and Dispatch
 
 Display the routing decision:
 
 ```
 **Input:** {first 80 chars of arguments}
+**Intent:** {skill} (confidence: {score})
+**Risk:** {low|medium|high} -- {top signal}
+**Ceremony:** {inline|lightweight-plan|full-plan-build-verify}
 **Routing to:** {chosen skill}
-**Reason:** {one-line explanation}
 ```
 
 Then invoke the chosen skill via the Skill tool, passing `$ARGUMENTS` as the args.
 
-**Special case for `/pbr:plan add`**: When routing to plan, check if `.planning/ROADMAP.md` exists first (via Read). If it doesn't, suggest `/pbr:begin` instead — the user needs to set up the project before they can add phases.
+**Special case for `/pbr:plan-phase add`**: When routing to plan, check if `.planning/ROADMAP.md` exists first (via Read). If it doesn't, suggest `/pbr:new-project` instead -- the user needs to set up the project before they can add phases.
 
-## Step 4 — No Follow-Up
+## Step 4 -- No Follow-Up
 
 After invoking the skill, your job is done. The dispatched skill handles everything from here (execution, commits, state updates). Do not add any additional output after the Skill tool call.
+
+## Feature Toggles
+
+These config properties in `.planning/config.json` control routing behavior:
+
+- `features.natural_language_routing: false` -- disables smart intent detection, falls back to static keyword table.
+- `features.adaptive_ceremony: false` -- disables risk-based ceremony selection, uses intent route directly.
+- `ceremony_level: "high"` -- forces full ceremony on everything (overrides risk classification).
+- `ceremony_level: "low"` -- forces inline ceremony on everything.
+- `ceremony_level: "auto"` -- (default) uses risk classification to determine ceremony.

package/plugins/pbr/skills/explore/SKILL.md

@@ -23,23 +23,36 @@ Then proceed to Step 1.
 
 You are running the **explore** skill. Your job is to help the user think through ideas that might become a todo, requirement, phase, decision, or nothing yet. This is Socratic conversation, not requirements gathering. No phase number is needed.
 
-This skill runs **inline** (no Task delegation), with optional Task() spawns for context loading and mid-conversation research.
+This skill runs **inline** (no Task delegation), with optional Task() spawns for context loading, upfront research, and mid-conversation research.
+
+**CRITICAL: Agent type rule** — When spawning ANY research or analysis Task(), ALWAYS use `subagent_type: "pbr:researcher"`. NEVER use `general-purpose`, `Explore`, or other non-PBR agent types. The PreToolUse hook will block non-PBR agents.
+
+---
+
+## References
+
+- `references/questioning.md` — Questioning philosophy, progressive depth layers, Socratic patterns, anti-patterns (checklist walking, corporate speak)
+- `references/ui-brand.md` — Status symbols, banners, checkpoint boxes, progress display
 
 ---
 
 ## Context Budget
 
 Reference: `skills/shared/context-budget.md` for the universal orchestrator rules.
+Reference: `skills/shared/agent-type-resolution.md` for agent type fallback when spawning Task() subagents.
 
 Additionally for this skill:
 - **Minimize** file reads — this is a thinking skill, not a code analysis skill
-- **Delegate** deep research to a researcher subagent if investigation exceeds 3-4 file reads
+- **Delegate** deep research to a researcher subagent if investigation exceeds the read threshold:
+  - At context_window_tokens < 500000 (200k model): delegate after 3-4 file reads
+  - At context_window_tokens >= 500000 (1M model): delegate after 12 file reads
+  Check `context_window_tokens` in `.planning/config.json` to determine which limit applies.
 
 ---
 
-## How /pbr:explore Differs from /pbr:discuss
+## How /pbr:explore Differs from /pbr:discuss-phase
 
-| | /pbr:discuss | /pbr:explore |
+| | /pbr:discuss-phase | /pbr:explore |
 |---|---|---|
 | Purpose | Make decisions for a phase | Discover what you actually want |
 | Structure | Pre-computed gray areas with options | Open-ended Socratic conversation |
@@ -105,10 +118,36 @@ Reference `skills/shared/domain-probes.md` for technology-specific follow-up que
 
 ---
 
+## Upfront Research Delegation
+
+When the user's initial request is research-heavy (e.g., "explore best practices for X", "research how other projects do Y", "compare approaches to Z"), delegate immediately to `pbr:researcher` agents rather than doing inline research.
+
+**Detection**: If `$ARGUMENTS` contains words like "research", "compare", "explore examples", "best practices", "how do others", or describes gathering external information — this is an upfront research task.
+
+**Pattern**: Spawn one or more `pbr:researcher` agents in parallel, then synthesize their findings inline:
+
+```
+Task({
+  subagent_type: "pbr:researcher",
+  prompt: "<research_assignment>
+    Topic: {specific research question from user's request}
+    Output: Return findings as structured markdown in your response.
+    Mode: external-research
+
+    {detailed research instructions}
+  </research_assignment>"
+})
+```
+
+After researchers complete, synthesize findings inline and continue the Socratic conversation with the user about what was discovered.
+
+---
+
 ## Mid-Conversation Research
 
 When a knowledge gap emerges during the conversation — you're unsure about a library, pattern, or approach — surface it explicitly.
 
+**CRITICAL -- DO NOT SKIP**: Present the following choice to the user via AskUserQuestion before proceeding:
 **Ask the user** using the **yes-no** pattern from `skills/shared/gate-prompts.md`:
   question: "I'm not sure about the best approach for {topic}. Research it now?"
   options:
@@ -117,14 +156,33 @@ When a knowledge gap emerges during the conversation — you're unsure about a l
 
 **If research now:**
 
-Display to the user: `◐ Spawning researcher...`
+Display to the user: `◆ Spawning researcher...`
+
+**Learnings injection (opt-in):** Check for relevant tech stack learnings:
+
+```bash
+node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js learnings query --tags "stack,tech,friction" 2>/dev/null
+```
+
+If non-empty JSON array returned:
+
+- Write to temp file: `node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js learnings query --tags "stack,tech,friction" > /tmp/pbr-learnings-$$.md`
+- Note path as `{learnings_temp_path}`; add as item 3 in the researcher's `files_to_read` block below
+
+If no learnings or command fails: omit the extra files_to_read entry.
 
 ```
 Task({
   subagent_type: "pbr:researcher",
-  prompt: "<research_assignment>
+  prompt: "<files_to_read>
+    CRITICAL: Read these files BEFORE any other action:
+    1. .planning/CONTEXT.md — locked decisions and constraints (if exists)
+    2. .planning/STATE.md — current project state (if exists)
+    {if learnings_temp_path exists}3. {learnings_temp_path} — cross-project learnings (tech stack patterns from past PBR projects){/if}
+  </files_to_read>
+  <research_assignment>
     Topic: {specific research question}
-    Output file: .planning/research/{topic-slug}.md
+    Output file: .planning/research/{topic-slug}.md (generate topic-slug via: node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js slug-generate "{topic}")
     Mode: project-research
 
     Research this specific question: {the question}
@@ -134,7 +192,15 @@ Task({
 })
 ```
 
-After the researcher completes, display: `✓ Research complete — results in .planning/research/{topic-slug}.md`
+If `{learnings_temp_path}` was produced above, replace `{if...}{/if}` with the actual line. If no learnings were found, omit item 3 entirely.
+
+After the researcher completes, check for completion markers in the Task() output:
+
+- If `## RESEARCH COMPLETE` is present: proceed normally
+- If `## RESEARCH BLOCKED` is present: display the blocker reason and offer to retry:
+  `⚠ Research blocked: {reason}. Try a different angle or continue without research.`
+
+Display: `✓ Research complete — results in .planning/research/{topic-slug}.md`
 
 Then:
 - Read ONLY the frontmatter and summary section of the research file (not the full document)
@@ -196,6 +262,7 @@ Want to adjust, add, or remove any of these?
 
 ### Step 3: Confirm
 
+**CRITICAL -- DO NOT SKIP**: Present the following choice to the user via AskUserQuestion before proceeding:
 Use the **output-routing** pattern from `skills/shared/gate-prompts.md`:
   question: "How do you want to handle these proposed outputs?"
 
@@ -209,6 +276,8 @@ Do NOT create any artifacts until the user selects "Approve all" on the final se
 
 ### Step 4: Create Artifacts
 
+**CRITICAL (no hook) -- DO NOT SKIP: Create target directories and write artifact files.**
+
 **Directory creation:** Before writing any artifact, ensure the target directory exists. Create `.planning/notes/`, `.planning/seeds/`, `.planning/research/`, or `.planning/todos/pending/` as needed if they don't already exist.
 
 Create only the approved artifacts. A single explore session can produce multiple outputs across different types.
@@ -234,11 +303,11 @@ After creating artifacts (or if user chose "Skip"), display:
 
 {Smart routing — pick the most relevant primary command:}
 - If a todo was created: **Manage tasks** → `/pbr:todo`
-- If a phase decision was captured: **Plan the phase** → `/pbr:plan {N}`
-- If a new phase was added: **Discuss the new phase** → `/pbr:discuss {N}`
-- If research questions were logged: **Plan with research** → `/pbr:plan {N}`
-- If current milestone is complete (STATE.md status is "milestone-complete"): **Start next milestone** → `/pbr:milestone new`
-- Default: **See project status** → `/pbr:status`
+- If a phase decision was captured: **Plan the phase** → `/pbr:plan-phase {N}`
+- If a new phase was added: **Discuss the new phase** → `/pbr:discuss-phase {N}`
+- If research questions were logged: **Plan with research** → `/pbr:plan-phase {N}`
+- If current milestone is complete (STATE.md status is "milestone-complete"): **Start next milestone** → `/pbr:new-milestone`
+- Default: **See project status** → `/pbr:progress`
 
 `{primary command}`
 
@@ -247,9 +316,9 @@ After creating artifacts (or if user chose "Skip"), display:
 
 
 **Also available:**
-- `/pbr:status` — see project status
+- `/pbr:progress` — see project status
 - `/pbr:continue` — execute next logical step
-- `/pbr:milestone new` — start a new milestone with new phases
+- `/pbr:new-milestone` — start a new milestone with new phases
 
 
 ```
@@ -260,7 +329,9 @@ After creating artifacts (or if user chose "Skip"), display:
 
 ### Todo
 
-Write to `.planning/todos/pending/{NNN}-{slug}.md` where NNN is a zero-padded 3-digit sequential number (001, 002, 003...). Scan both `.planning/todos/pending/` and `.planning/todos/done/` for the highest existing number, increment by 1, and zero-pad. Follow the format used by the existing todo skill.
+**CRITICAL: Write the todo file NOW. Do not skip this step.**
+
+Write to `.planning/todos/pending/{NNN}-{slug}.md` where NNN is a zero-padded 3-digit sequential number (001, 002, 003...). Scan both `.planning/todos/pending/` and `.planning/todos/done/` for the highest existing number, increment by 1, and zero-pad. Generate slug via CLI: `node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js slug-generate "{todo title}"`. Follow the format used by the existing todo skill.
 
 ### Requirement
 
@@ -294,7 +365,9 @@ Append to `.planning/ROADMAP.md` following the existing phase format. Assign the
 
 ### Note
 
-Write to `.planning/notes/{YYYY-MM-DD}-{slug}.md` where the date prefix is today's date in ISO format. Scan `.planning/notes/` to avoid filename collisions — if a file with the same date and slug exists, append `-2` (or increment).
+**CRITICAL: Write the note file NOW. Do not skip this step.**
+
+Write to `.planning/notes/{YYYY-MM-DD}-{slug}.md` where the date prefix is today's date in ISO format. Generate slug via CLI: `node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js slug-generate "{note title}"`. Scan `.planning/notes/` to avoid filename collisions — if a file with the same date and slug exists, append `-2` (or increment).
 
 ```markdown
 ---
@@ -309,7 +382,9 @@ topic: "{topic}"
 
 ### Seed
 
-Write to `.planning/seeds/SEED-{NNN}-{slug}.md` where NNN is a zero-padded 3-digit sequential number (001, 002, 003...). Scan `.planning/seeds/` for the highest existing SEED number, increment by 1, and zero-pad.
+**CRITICAL: Write the seed file NOW. Do not skip this step.**
+
+Write to `.planning/seeds/SEED-{NNN}-{slug}.md` where NNN is a zero-padded 3-digit sequential number (001, 002, 003...). Scan `.planning/seeds/` for the highest existing SEED number, increment by 1, and zero-pad. Generate slug via CLI: `node ${CLAUDE_PLUGIN_ROOT}/scripts/pbr-tools.js slug-generate "{seed title}"`.
 
 ```markdown
 ---
@@ -347,6 +422,8 @@ Stage only the files created during this session. Do not stage unrelated changes
 
 ## Error Handling
 
+Reference: `skills/shared/error-reporting.md` for branded error output patterns.
+
 ### Researcher agent fails
 If a mid-conversation researcher Task() fails, display:
 ```
@@ -368,8 +445,6 @@ If the briefing Task() fails:
 
 ## Anti-Patterns
 
-Reference: `skills/shared/universal-anti-patterns.md` for rules that apply to ALL skills.
-
 Additionally for this skill:
 
 1. **DO NOT** act like an interviewer — be a thinking partner

package/plugins/pbr/skills/fast/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: fast
+description: "Execute a trivial task inline without subagent overhead. No planning, no research — just do it and commit."
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+argument-hint: "<task description>"
+---
+
+**STOP — DO NOT READ THIS FILE. You are already reading it.**
+
+# /pbr:fast — Inline Trivial Task Execution
+
+Execute a trivial task directly in the current context. No subagents, no PLAN.md, no research. For tasks like: fix a typo, update a config value, add a missing import, rename a variable, add a .gitignore entry, bump a version.
+
+Use `/pbr:quick` for anything needing multi-step planning, research, or verification.
+
+## Step 0 — Banner
+
+```
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► FAST                                       ║
+╚══════════════════════════════════════════════════════════════╝
+```
+
+## Step 1 — Parse Task
+
+If `$ARGUMENTS` is empty, ask: "What's the quick fix? (one sentence)"
+
+Store as the task description.
+
+## Step 2 — Scope Check
+
+A task is trivial if it needs:
+- 3 or fewer file edits
+- No new dependencies or architecture changes
+- No research needed
+
+If the task seems non-trivial, say:
+
+```
+This looks like it needs planning. Use /pbr:quick instead:
+  /pbr:quick "{task description}"
+```
+
+And stop.
+
+## Step 3 — Execute Inline
+
+Do the work directly:
+
+1. Read the relevant file(s)
+2. Make the change(s) using Edit or Write
+3. Verify the change works (run existing tests if applicable)
+
+**No PLAN.md. No Task() spawn. Just do it.**
+
+## Step 4 — Commit
+
+Stage specific files (NEVER `git add .`) and commit:
+
+```bash
+git add {specific files}
+git commit -m "{type}(fast): {concise description}"
+```
+
+Use conventional commit types: fix, feat, docs, chore, refactor as appropriate.
+
+## Step 5 — Log to Quick Tasks
+
+If `.planning/quick/` exists, create a minimal tracking entry:
+
+1. Find next NNN: scan `.planning/quick/` for highest existing number + 1
+2. Create `.planning/quick/{NNN}-fast-{slug}/PLAN.md` with a one-line plan
+3. Create `.planning/quick/{NNN}-fast-{slug}/SUMMARY.md` with the commit hash and description
+
+This ensures fast tasks appear in state tracking alongside quick tasks.
+
+## Step 6 — Report
+
+```
+╔══════════════════════════════════════════════════════════════╗
+║  FAST ✓                                                      ║
+╚══════════════════════════════════════════════════════════════╝
+
+{commit hash} — {commit message}
+Files: {changed files}
+```
+
+## Anti-Patterns
+
+1. DO NOT spawn a Task() — fast mode is inline only
+2. DO NOT create elaborate plans — this is for trivial changes
+3. DO NOT use `git add .` — stage specific files
+4. DO NOT use fast mode for multi-file refactors — suggest `/pbr:quick`
+5. DO NOT skip the commit — every change gets committed