@sienklogic/plan-build-run 2.10.0 → 2.11.0

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

@@ -8,9 +8,9 @@ description: "Check planning directory integrity. Find and fix corrupted state."
 **Before ANY tool calls**, display this banner:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► HEALTH CHECK
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► HEALTH CHECK                               ║
+╚══════════════════════════════════════════════════════════════╝
 ```
 
 Then proceed to Step 1.
@@ -19,7 +19,7 @@ Then proceed to Step 1.
 
 You are running the **health** skill. Your job is to validate the integrity of the `.planning/` directory, report problems, and suggest targeted fixes. You never auto-repair anything.
 
-This skill runs **inline** and is **read-only** — it never modifies any files.
+This skill runs **inline**. It is read-only by default, but offers an optional **auto-fix** flow for common corruption patterns (see the Auto-Fix section below).
 
 ---
 
@@ -149,6 +149,58 @@ Glob for `.planning/phases/**/.PROGRESS-*` and `.planning/phases/**/.checkpoint-
 
 ---
 
+## Auto-Fix for Common Corruption Patterns
+
+After running all 10 checks and collecting results, if any of the following auto-fixable issues were found, offer to fix them.
+
+### Auto-Fixable Patterns
+
+| Pattern | Detection | Fix Action |
+|---------|-----------|------------|
+| Missing STATE.md frontmatter | Check 5 finds STATE.md without `---` block | Regenerate frontmatter from ROADMAP.md phase data (current_phase, total_phases, status) |
+| STATE.md phase_slug mismatch | Check 5/7 finds phase_slug doesn't match current phase directory name | Correct phase_slug to match the actual directory name in `.planning/phases/` |
+| Missing config.json | Check 1/2 finds no `.planning/config.json` | Create with default config template (same as `/pbr:setup` defaults) |
+| Orphaned .active-skill file | Check 10 or general scan finds `.planning/.active-skill` older than 1 hour | Delete the stale `.active-skill` file |
+| Empty phases directory | Check 3 finds `.planning/phases/` missing | Create the directory: `mkdir -p .planning/phases` |
+| STATE.md over 150 lines | Check 5 finds STATE.md exceeds 150 lines | Compact the `## Accumulated Context` section, keeping only the last 3 entries |
+
+### Auto-Fix Flow
+
+After displaying health check results, if any auto-fixable issues were detected:
+
+1. Count the auto-fixable issues and present:
+
+   Use AskUserQuestion:
+     question: "Found {N} auto-fixable issues. How should we handle them?"
+     header: "Fix?"
+     options:
+       - label: "Fix all"       description: "Apply all {N} fixes automatically"
+       - label: "Review each"   description: "Show each fix and confirm individually"
+       - label: "Skip"          description: "Do nothing — just report"
+
+2. If "Fix all": Apply all fixes in order, then display a summary:
+   ```
+   Auto-fix results:
+   - Fixed: {description of fix 1}
+   - Fixed: {description of fix 2}
+   ...
+   ```
+
+3. If "Review each": For each fixable issue, display:
+   ```
+   Issue: {description}
+   Fix: {what will be done}
+   ```
+   Then ask via AskUserQuestion (yes/no): "Apply this fix?"
+   - If yes: apply and display `- Fixed: {description}`
+   - If no: skip and display `- Skipped: {description}`
+
+4. If "Skip": Do nothing, continue to the rest of the output.
+
+**Note:** When auto-fix is active, the health skill is no longer strictly read-only. The `allowed-tools` frontmatter must include `Write` and `AskUserQuestion` for auto-fix to work. Update the frontmatter accordingly.
+
+---
+
 ## Bonus: Recent Decisions
 
 After all checks, look for `.planning/logs/decisions.jsonl`. If it exists, display the last 5 entries as `- {date}: {summary} (phase {N})`. If it does not exist, skip silently.
@@ -161,15 +213,17 @@ After all checks complete, display the branded result:
 
 **If all checks passed (0 failures):**
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► HEALTH CHECK PASSED ✓
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► HEALTH CHECK PASSED ✓                      ║
+╚══════════════════════════════════════════════════════════════╝
 
 {N} checks passed, {M} warnings
 
-───────────────────────────────────────────────────────────────
 
-## ▶ Next Up
+
+╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
 **Continue your workflow** — planning directory is healthy
 
@@ -177,40 +231,42 @@ After all checks complete, display the branded result:
 
 <sub>`/clear` first → fresh context window</sub>
 
-───────────────────────────────────────────────────────────────
+
 
 **Also available:**
 - `/pbr:continue` — execute next logical step
 - `/pbr:config` — adjust settings
 
-───────────────────────────────────────────────────────────────
+
 ```
 
 **If failures found:**
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► HEALTH CHECK FAILED ⚠
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► HEALTH CHECK FAILED ⚠                      ║
+╚══════════════════════════════════════════════════════════════╝
 
 {N} checks passed, {F} failures, {M} warnings
 
-───────────────────────────────────────────────────────────────
 
-## ▶ Next Up
+
+╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
 **Fix the failures** listed above, then re-run
 
 `/pbr:health`
 
-───────────────────────────────────────────────────────────────
+
 ```
 
 ---
 
 ## Anti-Patterns
 
-1. **DO NOT** modify any files — this is strictly read-only
-2. **DO NOT** auto-repair anything — present fixes and let the user decide
+1. **DO NOT** modify files without user consent — auto-fix requires explicit user approval via AskUserQuestion
+2. **DO NOT** auto-repair anything silently — always present fixes and let the user decide
 3. **DO NOT** skip checks that depend on missing files — report the dependency failure and continue
 4. **DO NOT** treat warnings as failures in the summary count — only count FAIL items
 5. **DO NOT** read full plan/summary contents — frontmatter and existence checks are sufficient

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

@@ -8,9 +8,9 @@ description: "Command reference and workflow guide for Plan-Build-Run."
 **Before ANY tool calls**, display this banner:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► COMMAND REFERENCE
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► COMMAND REFERENCE                          ║
+╚══════════════════════════════════════════════════════════════╝
 ```
 
 Then proceed to Step 1.
@@ -134,16 +134,16 @@ Skills automatically activate the appropriate context: `/pbr:build` uses dev con
 ## Getting Started
 
 ```
-───────────────────────────────────────────────────────────────
 
-## ▶ Next Up
+╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
 → `/pbr:begin` — start a new project
 → `/pbr:status` — check current project status
 → `/pbr:config` — configure workflow settings
 → `/pbr:help <command>` — detailed help for a specific command
 
-───────────────────────────────────────────────────────────────
 ```
 
 ## Getting Help

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

@@ -8,9 +8,9 @@ description: "Import external plans. Validates context, detects conflicts, gener
 **Before ANY tool calls**, display this banner:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► IMPORTING PLAN
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► IMPORTING PLAN                             ║
+╚══════════════════════════════════════════════════════════════╝
 ```
 
 Then proceed to Step 1.
@@ -47,11 +47,12 @@ Reference: `skills/shared/config-loading.md` for the tooling shortcut and config
 1. Parse `$ARGUMENTS` for phase number
 2. Parse optional `--from <filepath>` flag (path to the external document to import)
 3. Parse optional `--skip-checker` flag (skip plan validation step)
-4. Validate:
+4. **CRITICAL: Write .active-skill NOW.** Write the text "import" to `.planning/.active-skill` using the Write tool.
+5. Validate:
    - Phase exists in ROADMAP.md
    - Phase directory exists at `.planning/phases/{NN}-{slug}/`
-5. If no phase number given, read current phase from `.planning/STATE.md`
-6. Check for existing plans in the phase directory (glob for `*-PLAN.md`)
+6. If no phase number given, read current phase from `.planning/STATE.md`
+7. Check for existing plans in the phase directory (glob for `*-PLAN.md`)
    - If plans exist: ask user via AskUserQuestion: "Phase {N} already has plans. Replace them with imported plans?"
    - If yes: note that existing plans will be overwritten in Step 7
    - If no: stop
@@ -317,7 +318,7 @@ Follow the revision loop with:
 
 ### Step 7: Write PLAN.md Files (inline)
 
-Write each plan to `.planning/phases/{NN}-{slug}/{phase}-{plan_num}-PLAN.md`.
+Write each plan to `.planning/phases/{NN}-{slug}/PLAN-{plan_num}.md`.
 
 If existing plans are being replaced (user confirmed in Step 1):
 - Delete existing `*-PLAN.md` files in the phase directory before writing new ones
@@ -375,14 +376,18 @@ docs({phase}): import plans for phase {N} ({count} plans, {wave_count} waves)
 
 ---
 
-### Step 10: Confirm (inline)
+### Step 10: Cleanup
+
+Delete `.planning/.active-skill` if it exists. This must happen on all paths (success, partial, and failure) before reporting results.
+
+### Step 11: Confirm (inline)
 
 Present a summary of the import using the branded banner:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► IMPORT COMPLETE ✓
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► IMPORT COMPLETE ✓                          ║
+╚══════════════════════════════════════════════════════════════╝
 
 **Phase {N}: {name}** — {plan_count} plans imported
 
@@ -401,9 +406,9 @@ Wave execution order:
 Must-haves coverage: {count} truths across {plan_count} plans
 Requirements traced: {count}/{total} REQ-IDs covered
 
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
+╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
 **Build Phase {N}** — execute these imported plans
 
@@ -411,19 +416,18 @@ Requirements traced: {count}/{total} REQ-IDs covered
 
 <sub>`/clear` first → fresh context window</sub>
 
-───────────────────────────────────────────────────────────────
-
 **Also available:**
 - `/pbr:plan {N}` — re-plan from scratch if import needs rework
 - `/pbr:discuss {N}` — talk through details before building
 
-───────────────────────────────────────────────────────────────
 ```
 
 ---
 
 ## Error Handling
 
+**IMPORTANT:** On ALL error exits below, delete `.planning/.active-skill` if it exists before displaying the error message.
+
 ### Phase not found
 If the specified phase does not exist in ROADMAP.md, display:
 ```
@@ -492,7 +496,7 @@ Present remaining issues and ask user to decide: proceed or intervene.
 
 | File | Purpose | When |
 |------|---------|------|
-| `.planning/phases/{NN}-{slug}/{phase}-{NN}-PLAN.md` | Imported plan files | Step 7 |
+| `.planning/phases/{NN}-{slug}/PLAN-{NN}.md` | Imported plan files | Step 7 |
 | `.planning/ROADMAP.md` | Plans Complete + Status updated to `planned` | Step 8a |
 | `.planning/STATE.md` | Updated with plan status and import source | Step 8b |
 | `.planning/CONTEXT.md` | Updated if blockers surfaced new locked decisions | Step 8d |

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

@@ -8,9 +8,9 @@ description: "Manage milestones: new, complete, audit, gaps."
 **Before ANY tool calls**, display this banner:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► MILESTONE
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► MILESTONE                                  ║
+╚══════════════════════════════════════════════════════════════╝
 ```
 
 Then proceed to Step 1.
@@ -28,9 +28,9 @@ This skill runs **inline** for most subcommands, but spawns agents for `audit`.
 Reference: `skills/shared/context-budget.md` for the universal orchestrator rules.
 
 Additionally for this skill:
-- **Never** perform integration checks yourself — delegate to the integration-checker subagent
+- **Never** perform integration checks yourself — delegate to the integration-checker agent
 - **Minimize** reading audit and verification outputs — read only frontmatter and status fields
-- **Delegate** all cross-phase integration analysis to the integration-checker subagent
+- **Delegate** all cross-phase integration analysis to the integration-checker agent
 
 ---
 
@@ -155,9 +155,9 @@ Start a new milestone cycle with new phases.
 
 10. **Confirm** with branded output:
     ```
-    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-     PLAN-BUILD-RUN ► MILESTONE CREATED ✓
-    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+    ╔══════════════════════════════════════════════════════════════╗
+    ║  PLAN-BUILD-RUN ► MILESTONE CREATED ✓                        ║
+    ╚══════════════════════════════════════════════════════════════╝
 
     **Milestone: {name}** — {count} phases
 
@@ -166,9 +166,11 @@ Start a new milestone cycle with new phases.
     {N+1}. {name}
     ...
 
-    ───────────────────────────────────────────────────────────────
 
-    ## ▶ Next Up
+
+    ╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
     **Phase {N}: {name}** — start with discussion or planning
 
@@ -176,13 +178,13 @@ Start a new milestone cycle with new phases.
 
     <sub>`/clear` first → fresh context window</sub>
 
-    ───────────────────────────────────────────────────────────────
+
 
     **Also available:**
     - `/pbr:plan {N}` — skip discussion, plan directly
     - `/pbr:status` — see project status
 
-    ───────────────────────────────────────────────────────────────
+
     ```
 
 ---
@@ -259,14 +261,40 @@ Archive a completed milestone and prepare for the next one.
 
 5. **Archive milestone documents:**
 
+   **CRITICAL: Pre-flight safety checks BEFORE archiving. Do NOT skip this step.**
+
+   Before creating or moving anything, verify the destination is safe:
+   - Check if `.planning/milestones/{version}/` already exists
+   - If it exists AND contains files (phases/, STATS.md, etc.), STOP and display:
+     ```
+     ╔══════════════════════════════════════════════════════════════╗
+     ║  ERROR                                                       ║
+     ╚══════════════════════════════════════════════════════════════╝
+
+     Archive destination `.planning/milestones/{version}/` already contains files.
+     Completing this milestone would overwrite the existing archive.
+
+     **To fix:** Run `/pbr:health` or manually inspect `.planning/milestones/{version}/`.
+     Use a different version number (e.g., {version}.1) or remove the existing archive first.
+     ```
+     Ask the user via AskUserQuestion whether to use a different version or abort.
+   - Verify each source phase directory exists before attempting to move it
+   - If any source phase directory is missing, warn but continue with the phases that do exist
+
+   **CRITICAL: Create the archive directory .planning/milestones/{version}/ NOW. Do NOT skip this step.**
+
    Create a versioned archive directory and move phase directories into it:
    - `.planning/milestones/{version}/ROADMAP.md` — snapshot of ROADMAP.md at completion
-   - `.planning/milestones/{version}/REQUIREMENTS.md` — snapshot of REQUIREMENTS.md
+   - `.planning/milestones/{version}/REQUIREMENTS.md` — **CRITICAL: Copy REQUIREMENTS.md to archive NOW. Do NOT skip this step.** Snapshot of REQUIREMENTS.md
    - `.planning/milestones/{version}/STATS.md` — milestone statistics
    - `.planning/milestones/{version}/phases/{NN}-{slug}/` — move each milestone phase directory from `.planning/phases/` into the archive
 
+   **CRITICAL: Move phase directories from .planning/phases/ to archive NOW. Do NOT skip this step.**
+
    **Move phases:** For each phase belonging to this milestone, move (not copy) its directory from `.planning/phases/{NN}-{slug}/` to `.planning/milestones/{version}/phases/{NN}-{slug}/`. This keeps the active phases directory clean for the next milestone.
 
+   **CRITICAL: Write STATS.md to .planning/milestones/{version}/STATS.md NOW. Do NOT skip this step.**
+
    **Stats file content:**
 
    Read `skills/milestone/templates/stats-file.md.tmpl` for the stats file format. Fill in all `{variable}` placeholders with actual data gathered in Steps 3-4.
@@ -286,6 +314,8 @@ Archive a completed milestone and prepare for the next one.
 
    - Move validated requirements from active to completed section
 
+**CRITICAL: Update ROADMAP.md with collapsed milestone section NOW. Do NOT skip this step.**
+
 7. **Collapse completed phases in ROADMAP.md:**
    Replace detailed phase entries with collapsed summaries:
 
@@ -300,6 +330,8 @@ Archive a completed milestone and prepare for the next one.
    | {N+1}. {name} | Completed |
    ```
 
+**CRITICAL: Update STATE.md to mark milestone as complete NOW. Do NOT skip this step.**
+
 7b. **Update STATE.md:**
    - Update `.planning/STATE.md` to mark the milestone as complete
    - Clear the current milestone field or set status to "completed"
@@ -330,9 +362,9 @@ Archive a completed milestone and prepare for the next one.
 
 10. **Confirm** with branded output:
     ```
-    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-     PLAN-BUILD-RUN ► MILESTONE COMPLETE 🎉
-    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+    ╔══════════════════════════════════════════════════════════════╗
+    ║  PLAN-BUILD-RUN ► MILESTONE COMPLETE 🎉                      ║
+    ╚══════════════════════════════════════════════════════════════╝
 
     **{version}**
 
@@ -344,9 +376,11 @@ Archive a completed milestone and prepare for the next one.
     Archived to: .planning/milestones/{version}/
     Git tag: {version}
 
-    ───────────────────────────────────────────────────────────────
 
-    ## ▶ Next Up
+
+    ╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
     **Start the next milestone** — plan new features
 
@@ -354,13 +388,13 @@ Archive a completed milestone and prepare for the next one.
 
     <sub>`/clear` first → fresh context window</sub>
 
-    ───────────────────────────────────────────────────────────────
+
 
     **Also available:**
     - `/pbr:status` — see project status
     - `/pbr:help` — see all commands
 
-    ───────────────────────────────────────────────────────────────
+
     ```
 
 ---
@@ -384,7 +418,7 @@ Verify milestone completion with cross-phase integration checks.
 
    Display to the user: `◐ Spawning integration checker...`
 
-   Spawn `Task(subagent_type: "pbr:integration-checker")` with:
+   Spawn `Task(agent_type: "pbr:integration-checker")` with:
 
    ```
    You are integration-checker. Perform cross-phase integration verification.
@@ -425,15 +459,17 @@ Verify milestone completion with cross-phase integration checks.
 
    **If PASSED:**
    ```
-   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-    PLAN-BUILD-RUN ► MILESTONE AUDIT PASSED ✓
-   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+   ╔══════════════════════════════════════════════════════════════╗
+   ║  PLAN-BUILD-RUN ► MILESTONE AUDIT PASSED ✓                   ║
+   ╚══════════════════════════════════════════════════════════════╝
 
    All phases verified, integration checks passed, requirements covered.
 
-   ───────────────────────────────────────────────────────────────
 
-   ## ▶ Next Up
+
+   ╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
    **Complete the milestone** — archive and tag
 
@@ -441,28 +477,30 @@ Verify milestone completion with cross-phase integration checks.
 
    <sub>`/clear` first → fresh context window</sub>
 
-   ───────────────────────────────────────────────────────────────
+
 
    **Also available:**
    - `/pbr:milestone gaps` — address any minor issues first
    - `/pbr:status` — see project status
 
-   ───────────────────────────────────────────────────────────────
+
    ```
 
    **If GAPS FOUND:**
    ```
-   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-    PLAN-BUILD-RUN ► MILESTONE AUDIT — GAPS FOUND ⚠
-   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+   ╔══════════════════════════════════════════════════════════════╗
+   ║  PLAN-BUILD-RUN ► MILESTONE AUDIT — GAPS FOUND ⚠             ║
+   ╚══════════════════════════════════════════════════════════════╝
 
    Found {count} gaps:
    - {gap 1}
    - {gap 2}
 
-   ───────────────────────────────────────────────────────────────
 
-   ## ▶ Next Up
+
+   ╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
    **Close the gaps** — create fix phases
 
@@ -470,26 +508,28 @@ Verify milestone completion with cross-phase integration checks.
 
    <sub>`/clear` first → fresh context window</sub>
 
-   ───────────────────────────────────────────────────────────────
+
 
    **Also available:**
    - `/pbr:milestone complete` — proceed despite gaps
    - `/pbr:status` — see project status
 
-   ───────────────────────────────────────────────────────────────
+
    ```
 
    **If TECH DEBT:**
    ```
-   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-    PLAN-BUILD-RUN ► MILESTONE AUDIT — TECH DEBT ⚠
-   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+   ╔══════════════════════════════════════════════════════════════╗
+   ║  PLAN-BUILD-RUN ► MILESTONE AUDIT — TECH DEBT ⚠              ║
+   ╚══════════════════════════════════════════════════════════════╝
 
    Milestone functional but has {count} tech debt items.
 
-   ───────────────────────────────────────────────────────────────
 
-   ## ▶ Next Up
+
+   ╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
    **Address tech debt or proceed**
 
@@ -498,7 +538,7 @@ Verify milestone completion with cross-phase integration checks.
 
    <sub>`/clear` first → fresh context window</sub>
 
-   ───────────────────────────────────────────────────────────────
+
    ```
 
 ---
@@ -581,17 +621,19 @@ Create phases to close gaps found during an audit.
 
 9. **Confirm** with branded output:
    ```
-   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-    PLAN-BUILD-RUN ► GAP PHASES CREATED ✓
-   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+   ╔══════════════════════════════════════════════════════════════╗
+   ║  PLAN-BUILD-RUN ► GAP PHASES CREATED ✓                       ║
+   ╚══════════════════════════════════════════════════════════════╝
 
    Created {count} gap-closure phase(s):
    - Phase {N}: {name}
    - Phase {N+1}: {name}
 
-   ───────────────────────────────────────────────────────────────
 
-   ## ▶ Next Up
+
+   ╔══════════════════════════════════════════════════════════════╗
+║  ▶ NEXT UP                                                   ║
+╚══════════════════════════════════════════════════════════════╝
 
    **Plan the first gap-closure phase**
 
@@ -599,12 +641,12 @@ Create phases to close gaps found during an audit.
 
    <sub>`/clear` first → fresh context window</sub>
 
-   ───────────────────────────────────────────────────────────────
+
 
    **Also available:**
    - `/pbr:status` — see project status
 
-   ───────────────────────────────────────────────────────────────
+
    ```
 
 ---

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

@@ -8,9 +8,9 @@ description: "Zero-friction idea capture. Append, list, or promote notes to todo
 **Before ANY tool calls**, display this banner:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- PLAN-BUILD-RUN ► NOTE
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+╔══════════════════════════════════════════════════════════════╗
+║  PLAN-BUILD-RUN ► NOTE                                       ║
+╚══════════════════════════════════════════════════════════════╝
 ```
 
 Then proceed to Step 1.