@sienklogic/plan-build-run 2.50.0 → 2.52.0

package/plugins/copilot-pbr/skills/review/SKILL.md

@@ -3,6 +3,8 @@ name: review
 description: "Verify the build matched the plan. Automated checks + walkthrough with you."
 ---
 
+**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 ~7,600 tokens. Begin executing Step 1 immediately.**
+
 # /pbr:review — Phase Review and Verification
 
 You are the orchestrator for `/pbr:review`. This skill verifies that what was built matches what was planned. It runs automated three-layer checks against must-haves, then walks the user through a conversational UAT (user acceptance testing) for each deliverable. Your job is to present findings clearly and help the user decide what's good enough versus what needs fixes.
@@ -12,7 +14,7 @@ You are the orchestrator for `/pbr:review`. This skill verifies that what was bu
 Reference: `skills/shared/context-budget.md` for the universal orchestrator rules.
 
 Additionally for this skill:
-- **Minimize** reading agent output — read only VERIFICATION.md frontmatter for summaries
+- **Minimize** reading subagent output — read only VERIFICATION.md frontmatter for summaries
 
 ## Step 0 — Immediate Output
 
@@ -33,7 +35,7 @@ Where `{N}` is the phase number from `$ARGUMENTS`. Then proceed to Step 1.
 
 ### Event-Driven Auto-Verification
 
-When `features.goal_verification` is enabled and depth is "standard" or "comprehensive", event hooks automatically queue verification after executor completion. The hook writes `.planning/.auto-verify` as a signal file. The build skill's orchestrator detects this signal and invokes the verifier agent.
+When `features.goal_verification` is enabled and depth is "standard" or "comprehensive", the `event-handler.js` hook automatically queues verification after executor completion. The hook writes `.planning/.auto-verify` as a signal file. The build skill's orchestrator detects this signal and spawns the verifier agent.
 
 **This is additive**: `/pbr:review` can always be invoked manually regardless of auto-verification settings. If auto-verification already ran, `/pbr:review` re-runs verification (useful for re-checking after fixes).
 
@@ -64,20 +66,22 @@ Execute these steps in order.
 
 1. Parse `$ARGUMENTS` for phase number and `--auto-fix` flag
 2. Read `.planning/config.json`
-   **CRITICAL: Write .active-skill NOW.** Write the text "review" to `.planning/.active-skill` using the Write tool.
+   **CRITICAL (hook-enforced): Write .active-skill NOW.** Write the text "review" to `.planning/.active-skill` using the Write tool.
 3. Resolve depth profile: run `node ${PLUGIN_ROOT}/scripts/pbr-tools.js config resolve-depth` to get the effective feature/gate settings for the current depth. Store the result for use in later gating decisions.
 4. Validate:
    - Phase directory exists at `.planning/phases/{NN}-{slug}/`
    - SUMMARY.md files exist (phase has been built)
    - PLAN.md files exist (needed for must-have extraction)
 5. If no phase number given, read current phase from `.planning/STATE.md`
-6. If `.planning/.auto-verify` signal file exists, read it and note the auto-verification was already queued. Delete the signal file after reading (one-shot).
+6. If `.planning/.auto-verify` signal file exists, read it and note the auto-verification was already queued. Delete the signal file after reading (one-shot, same pattern as auto-continue.js).
 
 **Validation errors — use branded error boxes:**
 
 If no SUMMARY.md files:
 ```
-ERROR
+╔══════════════════════════════════════════════════════════════╗
+║  ERROR                                                       ║
+╚══════════════════════════════════════════════════════════════╝
 
 Phase {N} hasn't been built yet.
 
@@ -86,7 +90,9 @@ Phase {N} hasn't been built yet.
 
 If no PLAN.md files:
 ```
-ERROR
+╔══════════════════════════════════════════════════════════════╗
+║  ERROR                                                       ║
+╚══════════════════════════════════════════════════════════════╝
 
 Phase {N} has no plans.
 
@@ -114,30 +120,35 @@ Check if a VERIFICATION.md already exists from `/pbr:build`'s auto-verification
 
 ### Step 3: Automated Verification (delegated)
 
-**Depth profile gate:** Before invoking the verifier, resolve the depth profile. If `features.goal_verification` is false in the profile, skip automated verification and proceed directly to Step 5 (Conversational UAT). Note to user: "Automated verification skipped (depth: {depth}). Proceeding to manual review."
+**Depth profile gate:** Before spawning the verifier, resolve the depth profile. If `features.goal_verification` is false in the profile, skip automated verification and proceed directly to Step 5 (Conversational UAT). Note to user: "Automated verification skipped (depth: {depth}). Proceeding to manual review."
 
 #### Team Review Mode
 
 If `--teams` flag is present OR `config.parallelization.use_teams` is true:
 
 1. Create team output directory: `.planning/phases/{NN}-{slug}/team/` (if not exists)
-2. Display to the user: `Spawning 3 verifiers in parallel (functional, security, performance)...`
+2. Display to the user: `◐ Spawning 3 verifiers in parallel (functional, security, performance)...`
 
-   Invoke THREE `@verifier` agents in parallel:
+   Spawn THREE verifier agents in parallel using Task():
 
    **Agent 1 -- Functional Reviewer**:
-   - Invoke `@verifier` with: "You are the FUNCTIONAL REVIEWER in a review team. Focus on: must-haves met, code correctness, completeness, integration points. Write output to `.planning/phases/{NN}-{slug}/team/functional-VERIFY.md`."
+   - subagent_type: "pbr:verifier"
+   - Prompt includes: "You are the FUNCTIONAL REVIEWER in a review team. Focus on: must-haves met, code correctness, completeness, integration points. Write output to `.planning/phases/{NN}-{slug}/team/functional-VERIFY.md`."
 
    **Agent 2 -- Security Auditor**:
-   - Invoke `@verifier` with: "You are the SECURITY AUDITOR in a review team. Focus on: vulnerabilities, auth bypass paths, injection risks, secrets exposure, permission escalation. Write output to `.planning/phases/{NN}-{slug}/team/security-VERIFY.md`."
+   - subagent_type: "pbr:verifier"
+   - Prompt includes: "You are the SECURITY AUDITOR in a review team. Focus on: vulnerabilities, auth bypass paths, injection risks, secrets exposure, permission escalation. Write output to `.planning/phases/{NN}-{slug}/team/security-VERIFY.md`."
 
    **Agent 3 -- Performance Analyst**:
-   - Invoke `@verifier` with: "You are the PERFORMANCE ANALYST in a review team. Focus on: N+1 queries, memory leaks, unnecessary allocations, bundle size impact, blocking operations. Write output to `.planning/phases/{NN}-{slug}/team/performance-VERIFY.md`."
+   - subagent_type: "pbr:verifier"
+   - Prompt includes: "You are the PERFORMANCE ANALYST in a review team. Focus on: N+1 queries, memory leaks, unnecessary allocations, bundle size impact, blocking operations. Write output to `.planning/phases/{NN}-{slug}/team/performance-VERIFY.md`."
 
 3. Wait for all three to complete
-4. Display to the user: `Spawning synthesizer...`
+4. Display to the user: `◐ Spawning synthesizer...`
 
-   Invoke `@synthesizer` with: "Read all *-VERIFY.md files in `.planning/phases/{NN}-{slug}/team/`. Synthesize into a unified VERIFICATION.md. Merge pass/fail verdicts -- a must-have fails if ANY reviewer flags it. Combine gap lists. Security and performance findings go into dedicated sections."
+   Spawn synthesizer:
+   - subagent_type: "pbr:synthesizer"
+   - Prompt: "Read all *-VERIFY.md files in `.planning/phases/{NN}-{slug}/team/`. Synthesize into a unified VERIFICATION.md. Merge pass/fail verdicts -- a must-have fails if ANY reviewer flags it. Combine gap lists. Security and performance findings go into dedicated sections."
 5. Proceed to UAT walkthrough with the unified VERIFICATION.md
 
 If teams not enabled, proceed with existing single-verifier flow.
@@ -146,11 +157,19 @@ Reference: `references/agent-teams.md`
 
 #### Single-Verifier Flow (default)
 
-Display to the user: `Spawning verifier...`
+Display to the user: `◐ Spawning verifier...`
 
-Invoke the `@verifier` agent to run three-layer checks.
+Spawn a verifier Task() to run three-layer checks:
 
-**Path resolution**: Before constructing any agent prompt, resolve plugin root to its absolute path. Do not pass the variable literally in prompts. Use the resolved absolute path for any pbr-tools.js or template references included in the prompt.
+```
+Task({
+  subagent_type: "pbr:verifier",
+  // After verifier completes, check for: ## VERIFICATION COMPLETE
+  prompt: <verifier prompt>
+})
+```
+
+**Path resolution**: Before constructing any agent prompt, resolve `${PLUGIN_ROOT}` to its absolute path. Do not pass the variable literally in prompts — Task() contexts may not expand it. Use the resolved absolute path for any pbr-tools.js or template references included in the prompt.
 
 #### Verifier Prompt Template
 
@@ -159,7 +178,7 @@ Read `skills/review/templates/verifier-prompt.md.tmpl` and use its content as th
 **Prepend this block to the verifier prompt before sending:**
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/phases/{NN}-{slug}/PLAN-*.md — must-haves to verify against
 2. .planning/phases/{NN}-{slug}/SUMMARY-*.md — executor build summaries
 3. .planning/phases/{NN}-{slug}/VERIFICATION.md — prior verification results (if exists)
@@ -178,7 +197,7 @@ Wait for the verifier to complete.
 **After the verifier completes**, read VERIFICATION.md frontmatter and display a quick summary before the full results:
 
 ```
-Verifier: {passed}/{total} must-haves verified
+✓ Verifier: {passed}/{total} must-haves verified
 ```
 
 Then show a brief table of must-haves with pass/fail status:
@@ -186,15 +205,15 @@ Then show a brief table of must-haves with pass/fail status:
 ```
 | Must-Have | Status |
 |-----------|--------|
-| {name}    | PASS   |
-| {name}    | FAIL   |
+| {name}    | ✓      |
+| {name}    | ✗      |
 ```
 
 Then display the overall verdict (`PASSED`, `GAPS FOUND`, or `HUMAN NEEDED`) before proceeding to the full results presentation.
 
 ### Step 3a: Spot-Check Verifier Output
 
-CRITICAL: Verify verifier output before proceeding.
+CRITICAL (no hook): Verify verifier output before proceeding.
 
 1. **VERIFICATION.md exists**: Check `.planning/phases/{NN}-{slug}/VERIFICATION.md` exists on disk
 2. **Status field present**: Read VERIFICATION.md frontmatter — verify `status` field is present and is one of: pass, fail, partial
@@ -232,16 +251,16 @@ The same gaps have persisted across {attempt} verification attempts.
 Remaining gaps: {count}
 ```
 
-Use the multi-option-escalation pattern from `skills/shared/gate-prompts.md`:
+Use AskUserQuestion (pattern: multi-option-escalation from `skills/shared/gate-prompts.md`):
   question: "Phase {N} has failed verification {attempt} times with {count} persistent gaps. How should we proceed?"
   header: "Escalate"
   options:
     - label: "Accept gaps"   description: "Mark as complete-with-gaps and move on"
     - label: "Re-plan"       description: "Go back to /pbr:plan {N} with gap context"
-    - label: "Debug"         description: "Invoke /pbr:debug to investigate root causes"
+    - label: "Debug"         description: "Spawn /pbr:debug to investigate root causes"
     - label: "Retry"         description: "Try one more verification cycle"
 
-- **If user selects "Accept gaps":** Follow up with a second question:
+- **If user selects "Accept gaps":** Follow up with a second AskUserQuestion:
     question: "Accept all gaps or pick specific ones to override?"
     header: "Override?"
     options:
@@ -348,7 +367,7 @@ If all automated checks and UAT items passed:
    4. Update the `Status` column to `verified`
    5. Update the `Completed` column to the current date (YYYY-MM-DD)
    6. Save the file — do NOT skip this step
-2. Update `.planning/STATE.md` **(CRITICAL — update BOTH frontmatter AND body):**
+2. Update `.planning/STATE.md` **(CRITICAL (no hook) — update BOTH frontmatter AND body):**
    - Frontmatter: `status: "verified"`, `progress_percent`, `last_activity`, `last_command`
    - Body `## Current Position`: `Status:` line, `Last activity:` line, `Progress:` bar
    - These MUST stay in sync — see `skills/shared/state-update.md`
@@ -358,11 +377,12 @@ If all automated checks and UAT items passed:
 
 Use the branded output from `references/ui-formatting.md`:
 - If more phases remain: use the "Phase Complete" banner template
-- If this was the last phase: use the "Milestone Complete" banner template
+- If this was the last phase in the current milestone: use the "Milestone Complete" banner template
+- **Milestone boundary detection:** Read ROADMAP.md and find the `## Milestone:` section containing the current phase. Check its `**Phases:** start - end` range. If the current phase equals `end`, this is the last phase in the milestone.
 - Always include the "Next Up" routing block
 
 4. If `gates.confirm_transition` is true in config AND `features.auto_advance` is NOT true:
-   - Use the yes-no pattern from `skills/shared/gate-prompts.md`:
+   - Use AskUserQuestion (pattern: yes-no from `skills/shared/gate-prompts.md`):
      question: "Phase {N} verified. Ready to move to Phase {N+1}?"
      header: "Continue?"
      options:
@@ -372,9 +392,9 @@ Use the branded output from `references/ui-formatting.md`:
    - If "No" or "Other": stop
 
 5. **If `features.auto_advance` is `true` AND `mode` is `autonomous` AND more phases remain:**
-   - Chain directly to plan next phase
-   - This continues the build->review->plan cycle automatically
-   - **If this is the last phase:** HARD STOP — do NOT auto-advance past milestone boundaries
+   - Chain directly to plan: `Skill({ skill: "pbr:plan", args: "{N+1}" })`
+   - This continues the build→review→plan cycle automatically
+   - **If this is the last phase in the current milestone:** HARD STOP — do NOT auto-advance past milestone boundaries. Display: "auto_advance pauses at milestone boundaries — your sign-off is required."
 
 #### Gaps Found WITH `--auto-fix`
 
@@ -382,9 +402,16 @@ If gaps were found and `--auto-fix` was specified:
 
 **Step 6a: Diagnose**
 
-Display to the user: `Spawning debugger...`
+Display to the user: `◐ Spawning debugger...`
+
+Spawn a debugger Task() to analyze each failure:
 
-Invoke the `@debugger` agent to analyze each failure.
+```
+Task({
+  subagent_type: "pbr:debugger",
+  prompt: <debugger prompt>
+})
+```
 
 ##### Debugger Prompt Template
 
@@ -393,7 +420,7 @@ Read `skills/review/templates/debugger-prompt.md.tmpl` and use its content as th
 **Prepend this block to the debugger prompt before sending:**
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/phases/{NN}-{slug}/VERIFICATION.md — gaps and failure details
 2. .planning/phases/{NN}-{slug}/SUMMARY-*.md — what was built
 3. .planning/phases/{NN}-{slug}/PLAN-*.md — original plan must-haves
@@ -407,9 +434,16 @@ CRITICAL: Read these files BEFORE any other action:
 
 **Step 6b: Create Gap-Closure Plans**
 
-After receiving the root cause analysis, display to the user: `Spawning planner (gap closure)...`
+After receiving the root cause analysis, display to the user: `◐ Spawning planner (gap closure)...`
+
+Spawn the planner in gap-closure mode:
 
-Invoke the `@planner` agent in gap-closure mode.
+```
+Task({
+  subagent_type: "pbr:planner",
+  prompt: <gap planner prompt>
+})
+```
 
 ##### Gap Planner Prompt Template
 
@@ -418,7 +452,7 @@ Read `skills/review/templates/gap-planner-prompt.md.tmpl` and use its content as
 **Prepend this block to the gap planner prompt before sending:**
 ```
 <files_to_read>
-CRITICAL: Read these files BEFORE any other action:
+CRITICAL (no hook): Read these files BEFORE any other action:
 1. .planning/phases/{NN}-{slug}/VERIFICATION.md — gaps to close
 2. .planning/phases/{NN}-{slug}/PLAN-*.md — existing plans for context
 3. .planning/CONTEXT.md — locked decisions and constraints (if exists)
@@ -435,8 +469,8 @@ CRITICAL: Read these files BEFORE any other action:
 **Step 6c: Validate gap-closure plans (conditional)**
 
 If `features.plan_checking` is true in config:
-- Display to the user: `Spawning plan checker...`
-- Invoke `@plan-checker` on the new gap-closure plans
+- Display to the user: `◐ Spawning plan checker...`
+- Spawn plan checker Task() on the new gap-closure plans
 - Same process as `/pbr:plan` Step 6
 
 **Step 6d: Present gap-closure plans to user**
@@ -452,7 +486,7 @@ Plans:
   {plan_id}: {name} — fixes: {gap description} ({difficulty})
   {plan_id}: {name} — fixes: {gap description} ({difficulty})
 
-Use the approve-revise-abort pattern from `skills/shared/gate-prompts.md`:
+Use AskUserQuestion (pattern: approve-revise-abort from `skills/shared/gate-prompts.md`):
   question: "Approve these {count} gap-closure plans?"
   header: "Approve?"
   options:
@@ -483,7 +517,7 @@ Phase {N}: {name} — Gaps Found
 2. {gap description}
    ...
 
-Use the multi-option-gaps pattern from `skills/shared/gate-prompts.md`:
+Use AskUserQuestion (pattern: multi-option-gaps from `skills/shared/gate-prompts.md`):
   question: "{count} verification gaps need attention. How should we proceed?"
   header: "Gaps"
   options:
@@ -548,9 +582,11 @@ After Step 3, also check cross-phase integration:
 ## Error Handling
 
 ### Verifier agent fails
-If the verifier agent fails, display:
+If the verifier Task() fails, display:
 ```
-ERROR
+╔══════════════════════════════════════════════════════════════╗
+║  ERROR                                                       ║
+╚══════════════════════════════════════════════════════════════╝
 
 Automated verification failed.
 
@@ -560,7 +596,7 @@ Fall back to manual UAT only (skip automated checks).
 
 ### No must-haves to check
 If plans have empty must_haves:
-- Warn user: "Plans don't have defined must-haves. UAT will be based on plan descriptions only."
+- Warn user: `⚠ Plans don't have defined must-haves. UAT will be based on plan descriptions only.`
 - Use SUMMARY.md content as the basis for UAT
 
 ### User can't verify something
@@ -570,9 +606,11 @@ If user can't verify an item (e.g., needs server running, needs credentials):
 - Suggest how to verify later
 
 ### Debugger fails during auto-fix
-If the debugger agent fails, display:
+If the debugger Task() fails, display:
 ```
-ERROR
+╔══════════════════════════════════════════════════════════════╗
+║  ERROR                                                       ║
+╚══════════════════════════════════════════════════════════════╝
 
 Auto-diagnosis failed.
 
@@ -588,7 +626,7 @@ Ask user: "Would you like to proceed with gap-closure plans without root cause a
 |------|---------|------|
 | `.planning/phases/{NN}-{slug}/VERIFICATION.md` | Verification report | Step 3 (created or updated with UAT) |
 | `.planning/phases/{NN}-{slug}/*-PLAN.md` | Gap-closure plans | Step 6b (--auto-fix only) |
-| `.planning/ROADMAP.md` | Status -> `verified` + Completed date | Step 6 |
+| `.planning/ROADMAP.md` | Status → `verified` + Completed date | Step 6 |
 | `.planning/STATE.md` | Updated with review status | Step 6 |
 
 ---

package/plugins/copilot-pbr/skills/scan/SKILL.md

@@ -3,6 +3,8 @@ name: scan
 description: "Analyze an existing codebase. Maps structure, architecture, conventions, and concerns."
 ---
 
+**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 ~7,600 tokens. Begin executing Step 1 immediately.**
+
 ## Step 0 — Immediate Output
 
 **Before ANY tool calls**, display this banner:
@@ -227,6 +229,7 @@ Top concerns:
 Then use the "Next Up" routing block:
 ```
 
+
 ╔══════════════════════════════════════════════════════════════╗
 ║  ▶ NEXT UP                                                   ║
 ╚══════════════════════════════════════════════════════════════╝
@@ -237,10 +240,13 @@ Then use the "Next Up" routing block:
 
 <sub>`/clear` first → fresh context window</sub>
 
+
+
 **Also available:**
 - `/pbr:milestone new` — create a milestone to address concerns
 - `/pbr:status` — see project status
 
+
 ```
 
 ### Step 7: Git Integration

package/plugins/copilot-pbr/skills/setup/SKILL.md

@@ -3,6 +3,8 @@ name: setup
 description: "Onboarding wizard. Initialize project, select models, verify setup."
 ---
 
+**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 ~7,600 tokens. Begin executing Step 1 immediately.**
+
 ## Step 0 — Immediate Output
 
 **Before ANY tool calls**, display this banner:

package/plugins/copilot-pbr/skills/shared/commit-planning-docs.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/commit-planning-docs.md -->
 # Commit Planning Docs Pattern
 
 Standard pattern for committing planning artifacts to git. Reference this fragment in skills that create or modify `.planning/` files.

package/plugins/copilot-pbr/skills/shared/config-loading.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/config-loading.md -->
 # Config Loading Pattern
 
 Standard pattern for loading `.planning/config.json` fields at the start of a skill invocation.

package/plugins/copilot-pbr/skills/shared/context-budget.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/context-budget.md -->
 # Context Budget Rules
 
 Standard rules for keeping orchestrator context lean. Reference this fragment in skills that spawn Task() agents.

package/plugins/copilot-pbr/skills/shared/context-loader-task.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/context-loader-task.md -->
 # Context Loader Task Pattern
 
 Standard pattern for spawning a lightweight Task() to build a project briefing before the main skill logic runs. Used by skills that need project context but want to keep the orchestrator lean.

package/plugins/copilot-pbr/skills/shared/digest-select.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/digest-select.md -->
 # Digest-Select Pattern
 
 Selective reading depth for prior phase SUMMARY.md files. Saves tokens by reading only what is needed based on the relationship to the current phase.

package/plugins/copilot-pbr/skills/shared/domain-probes.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/domain-probes.md -->
 # Domain-Aware Probing Patterns
 
 Shared reference for `/pbr:explore`, `/pbr:begin`, and `/pbr:discuss`.

package/plugins/copilot-pbr/skills/shared/gate-prompts.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/gate-prompts.md -->
 # Gate Prompt Patterns
 
 > Referenced by: plan, build, import, scan, review, milestone, config, status, resume, quick, begin, discuss, explore, debug skills

package/plugins/copilot-pbr/skills/shared/phase-argument-parsing.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/phase-argument-parsing.md -->
 # Phase Argument Parsing
 
 How skills parse and validate phase number arguments from `$ARGUMENTS`.

package/plugins/copilot-pbr/skills/shared/revision-loop.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/revision-loop.md -->
 # Revision Loop Pattern
 
 Standard pattern for iterative agent revision with feedback. Used when a checker/validator finds issues and the producing agent needs to revise its output.

package/plugins/copilot-pbr/skills/shared/state-update.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/state-update.md -->
 # STATE.md Update Pattern
 
 Standard pattern for updating `.planning/STATE.md`. Include this fragment in skills that modify project state.

package/plugins/copilot-pbr/skills/shared/universal-anti-patterns.md

@@ -1,4 +1,3 @@
-<!-- canonical: ../../../pbr/skills/shared/universal-anti-patterns.md -->
 # Universal Anti-Patterns
 
 Rules that apply to ALL skills. Individual skills may have additional skill-specific anti-patterns listed in their own SKILL.md.
@@ -26,7 +25,7 @@ These rules prevent context rot -- quality degradation as the context window fil
 
 ## Task/Subagent Rules (apply to every skill)
 
-10. **Never** invoke `Skill()` inside a `Task()` subagent -- the Skill tool is not available in subagent contexts. Subagents spawned by `Task()` cannot resolve `/pbr:*` skill prefixes, so `Skill({ skill: "pbr:plan" })` will silently fail. Instead, chain skills at the orchestrator level (return control to the orchestrator, then call `Skill()` from there). For subagent work, use `subagent_type: "pbr:{agent}"` which auto-loads agent definitions.
+10. **Never** invoke `Skill()` inside a `Task()` subagent -- the Skill tool is not available in subagent contexts. Agents spawned by `Task()` cannot resolve `/pbr:*` skill prefixes, so `Skill({ skill: "pbr:plan" })` will silently fail. Instead, chain skills at the orchestrator level (return control to the orchestrator, then call `Skill()` from there). For subagent work, use `subagent_type: "pbr:{agent}"` which auto-loads agent definitions.
 
 ## Behavioral Rules (apply to every skill)
 

package/plugins/copilot-pbr/skills/status/SKILL.md

@@ -3,6 +3,8 @@ name: status
 description: "Show current project status and suggest what to do next."
 ---
 
+**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 ~7,600 tokens. Begin executing Step 1 immediately.**
+
 ## Step 0 — Immediate Output
 
 **Before ANY tool calls**, display this banner:
@@ -48,7 +50,9 @@ Read the following files (skip any that don't exist):
 1. **`.planning/config.json`** — Project settings
    - If this doesn't exist, display:
      ```
-     ERROR
+     ╔══════════════════════════════════════════════════════════════╗
+     ║  ERROR                                                       ║
+     ╚══════════════════════════════════════════════════════════════╝
 
      No Plan-Build-Run project found.
 
@@ -240,8 +244,8 @@ Generate a 20-character progress bar:
 ```
 
 Use Unicode block characters:
-- Filled: full block (U+2588)
-- Empty: light shade (U+2591)
+- Filled: `█` (full block, U+2588)
+- Empty: `░` (light shade, U+2591)
 
 ### Status Indicators
 
@@ -263,57 +267,59 @@ Based on the project state, suggest the single most logical next action:
 
 ```
 1. Is there paused work (.continue-here.md)?
-   YES -> "Resume your work: `/pbr:resume`"
+   YES → "Resume your work: `/pbr:resume`"
 
 2. Is there a verification with gaps?
-   YES -> "Fix verification gaps: `/pbr:plan {N} --gaps`"
+   YES → "Fix verification gaps: `/pbr:plan {N} --gaps`"
 
 3. Is the current phase planned but not built?
-   YES -> "Build the current phase: `/pbr:build {N}`"
+   YES → "Build the current phase: `/pbr:build {N}`"
 
 4. Is the current phase built but not reviewed?
-   YES -> "Review what was built: `/pbr:review {N}`"
+   YES → "Review what was built: `/pbr:review {N}`"
 
 5. Is the current phase verified (complete)?
-   YES -> Is there a next phase?
-     YES -> Was next phase already planned?
-       YES -> Does it need re-planning? (dependency phase changed)
-         YES -> "Re-plan with updated context: `/pbr:plan {N+1}`"
-         NO -> "Build the next phase: `/pbr:build {N+1}`"
-       NO -> "Plan the next phase: `/pbr:plan {N+1}`"
-     NO -> "All phases complete! Your next steps:\n       -> /pbr:milestone audit — verify cross-phase integration (recommended)\n       -> /pbr:milestone complete — archive this milestone and create a git tag\n       -> /pbr:milestone new — start planning the next set of features"
+   YES → Is there a next phase?
+     YES → Was next phase already planned?
+       YES → Does it need re-planning? (dependency phase changed)
+         YES → "Re-plan with updated context: `/pbr:plan {N+1}`"
+         NO → "Build the next phase: `/pbr:build {N+1}`"
+       NO → "Plan the next phase: `/pbr:plan {N+1}`"
+     NO → Check for existing `*-MILESTONE-AUDIT.md` in `.planning/`:\n       IF audit passed → "All phases complete and audited! `/pbr:milestone complete` to archive and tag."\n       IF audit has gaps → "Audit found gaps. `/pbr:milestone gaps` to address them."\n       IF no audit → "All phases complete! `/pbr:milestone audit` to verify cross-phase integration (recommended), then `/pbr:milestone complete`."
 
 6. Is the current phase not started?
-   YES -> Has it been discussed?
-     YES -> "Plan this phase: `/pbr:plan {N}`"
-     NO -> "Start with a discussion: `/pbr:discuss {N}` or jump to `/pbr:plan {N}`"
+   YES → Has it been discussed?
+     YES → "Plan this phase: `/pbr:plan {N}`"
+     NO → "Start with a discussion: `/pbr:discuss {N}` or jump to `/pbr:plan {N}`"
 
 7. Active debug sessions?
-   YES -> "Continue debugging: `/pbr:debug`"
+   YES → "Continue debugging: `/pbr:debug`"
 
 8. Nothing active?
-   -> "Start your project: `/pbr:begin`"
+   → "Start your project: `/pbr:begin`"
 ```
 
 **If only one reasonable next action exists**, present it with branded routing:
 
 ```
----
 
-## Next Up
+
+╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
 **{brief explanation}**
 
 `{suggested command}`
 
-`/clear` first for a fresh context window
+<sub>`/clear` first → fresh context window</sub>
+
 
----
 ```
 
 **If multiple reasonable next actions exist** (2-3 alternatives), use the **action-routing** pattern (see `skills/shared/gate-prompts.md`):
 
-Present options:
+Use AskUserQuestion:
   question: "What would you like to do next?"
   header: "Next Step"
   options:
@@ -347,7 +353,10 @@ Build options dynamically from the decision tree results. Always include "Someth
 
 ### All phases complete
 - Celebrate briefly: "All phases complete!"
-- Suggest: `/pbr:milestone audit` to verify cross-phase integration (recommended first)
+- Check for existing audit report: look for `*-MILESTONE-AUDIT.md` in `.planning/`
+  - **If audit exists and passed:** Suggest `/pbr:milestone complete` to archive (audit already done)
+  - **If audit exists with gaps:** Suggest `/pbr:milestone gaps` to address issues
+  - **If no audit exists:** Suggest `/pbr:milestone audit` to verify cross-phase integration (recommended first)
 - Then: `/pbr:milestone complete` to archive the milestone and tag it
 - Or: `/pbr:milestone new` to start the next set of features
 
@@ -382,7 +391,7 @@ This skill should be fast. It's a status check, not an analysis.
 - Read plan file contents (just check existence)
 - Run Bash commands except for Step 1b (2-3 `pbr-tools` calls only when `local_llm.enabled: true`, skipped entirely otherwise)
 - Modify any files
-- Invoke any agents
+- Spawn any Task agents
 
 ---
 

package/plugins/copilot-pbr/skills/test/SKILL.md

@@ -3,7 +3,7 @@ name: test
 description: "Generate tests for completed phase code. Detects test framework and targets key files."
 ---
 
-**STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by the plugin system. Using the Read tool on this SKILL.md file wastes ~7,600 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 ~7,600 tokens. Begin executing Step 1 immediately.**
 
 # /pbr:test — Post-Phase Test Generation
 
@@ -125,7 +125,7 @@ Output: tests/auth/login.test.js
 For each target file (or batch of related files), spawn an executor agent:
 
 ```
-Spawn agent_type: "pbr:executor"
+Spawn subagent_type: "pbr:executor"
 
 Task: Generate tests for the following file(s):
 

package/plugins/copilot-pbr/skills/todo/SKILL.md

@@ -3,6 +3,8 @@ name: todo
 description: "File-based persistent todos. Add, list, complete — survives sessions."
 ---
 
+**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 ~7,600 tokens. Begin executing Step 1 immediately.**
+
 ## Step 0 — Immediate Output
 
 **Before ANY tool calls**, display this banner:

package/plugins/copilot-pbr/templates/CONTEXT.md.tmpl

@@ -1,4 +1,3 @@
-<!-- canonical: ../../pbr/templates/CONTEXT.md.tmpl -->
 # CONTEXT.md Template
 
 > Referenced by: begin skill (Step 9c), discuss skill, plan skill

package/plugins/copilot-pbr/templates/INTEGRATION-REPORT.md.tmpl

@@ -1,4 +1,3 @@
-<!-- canonical: ../../pbr/templates/INTEGRATION-REPORT.md.tmpl -->
 <!-- Source: agents/integration-checker.md | Purpose: Output format for cross-phase integration verification reports -->
 
 ```markdown