@sienklogic/plan-build-run 2.50.0 → 2.52.0

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

@@ -3,6 +3,9 @@ name: milestone
 description: "Manage milestones: new, complete, audit, gaps."
 argument-hint: "new|complete|audit|gaps [version]"
 ---
+<!-- markdownlint-disable MD012 MD046 -->
+
+**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
 
@@ -29,9 +32,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 agent
+- **Never** perform integration checks yourself — delegate to the integration-checker subagent
 - **Minimize** reading audit and verification outputs — read only frontmatter and status fields
-- **Delegate** all cross-phase integration analysis to the integration-checker agent
+- **Delegate** all cross-phase integration analysis to the integration-checker subagent
 
 ---
 
@@ -147,7 +150,7 @@ Start a new milestone cycle with new phases.
    - **Status:** In progress
    ```
 
-**CRITICAL -- DO NOT SKIP: Update STATE.md frontmatter AND body with new milestone info.**
+**CRITICAL (no hook) -- DO NOT SKIP: Update STATE.md frontmatter AND body with new milestone info.**
 
 8. **Update STATE.md:**
    - Set current phase to the first new phase
@@ -158,39 +161,7 @@ Start a new milestone cycle with new phases.
    docs(planning): start milestone "{name}" (phases {start}-{end})
    ```
 
-10. **Confirm** with branded output:
-    ```
-    ╔══════════════════════════════════════════════════════════════╗
-    ║  PLAN-BUILD-RUN ► MILESTONE CREATED ✓                        ║
-    ╚══════════════════════════════════════════════════════════════╝
-
-    **Milestone: {name}** — {count} phases
-
-    Phases:
-    {N}. {name}
-    {N+1}. {name}
-    ...
-
-
-
-    ╔══════════════════════════════════════════════════════════════╗
-    ║  ▶ NEXT UP                                                   ║
-    ╚══════════════════════════════════════════════════════════════╝
-
-    **Phase {N}: {name}** — start with discussion or planning
-
-    `/pbr:discuss {N}`
-
-    <sub>`/clear` first → fresh context window</sub>
-
-
-
-    **Also available:**
-    - `/pbr:plan {N}` — skip discussion, plan directly
-    - `/pbr:status` — see project status
-
-
-    ```
+10. **Confirm** with branded output — read `skills/milestone/templates/new-output.md.tmpl` and fill in `{name}` (milestone name), `{count}` (phase count), `{N}` (first phase number).
 
 ---
 
@@ -249,7 +220,7 @@ Dry-run of milestone completion — shows what would happen without making any c
    Ready to complete? Run: /pbr:milestone complete v{version}
    ```
 
-**CRITICAL**: This subcommand is READ-ONLY. Do not create directories, move files, modify STATE.md, modify ROADMAP.md, or create git tags. Only read and display.
+**CRITICAL (no hook)**: This subcommand is READ-ONLY. Do not create directories, move files, modify STATE.md, modify ROADMAP.md, or create git tags. Only read and display.
 
 ---
 
@@ -325,7 +296,7 @@ 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.**
+   **CRITICAL (no hook): 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
@@ -345,19 +316,19 @@ Archive a completed milestone and prepare for the next one.
    - 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.**
+   **CRITICAL (no hook): 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` — **CRITICAL: Copy REQUIREMENTS.md to archive NOW. Do NOT skip this step.** Snapshot of REQUIREMENTS.md
+   - `.planning/milestones/{version}/REQUIREMENTS.md` — **CRITICAL (no hook): 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.**
+   **CRITICAL (no hook): 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.**
+   **CRITICAL (no hook): Write STATS.md to .planning/milestones/{version}/STATS.md NOW. Do NOT skip this step.**
 
    **Stats file content:**
 
@@ -378,7 +349,7 @@ 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.**
+**CRITICAL (no hook): 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:
@@ -394,7 +365,7 @@ 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.**
+**CRITICAL (no hook): 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
@@ -415,7 +386,7 @@ Archive a completed milestone and prepare for the next one.
 
 7d. **Aggregate learnings from milestone phases:**
 
-**CRITICAL: Run learnings aggregation NOW. Do NOT skip this step.**
+**CRITICAL (no hook): Run learnings aggregation NOW. Do NOT skip this step.**
 
 ```bash
 node ${PLUGIN_ROOT}/scripts/milestone-learnings.js .planning/milestones/{version} --project {project-name-from-STATE.md}
@@ -478,42 +449,7 @@ If `config.deployment.smoke_test_command` is set and non-empty:
 
    This is advisory only — the milestone is already archived. Surface it as a potential issue for the user to investigate.
 
-10. **Confirm** with branded output:
-    ```
-    ╔══════════════════════════════════════════════════════════════╗
-    ║  PLAN-BUILD-RUN ► MILESTONE COMPLETE 🎉                      ║
-    ╚══════════════════════════════════════════════════════════════╝
-
-    **{version}**
-
-    Stats:
-    - {count} phases, {count} plans
-    - {count} commits, {lines} lines of code
-    - {duration} days
-
-    Archived to: .planning/milestones/{version}/
-    Git tag: {version}
-
-
-
-    ╔══════════════════════════════════════════════════════════════╗
-    ║  ▶ NEXT UP                                                   ║
-    ╚══════════════════════════════════════════════════════════════╝
-
-    **Start the next milestone** — plan new features
-
-    `/pbr:milestone new`
-
-    <sub>`/clear` first → fresh context window</sub>
-
-
-
-    **Also available:**
-    - `/pbr:status` — see project status
-    - `/pbr:help` — see all commands
-
-
-    ```
+10. **Confirm** with branded output — read `skills/milestone/templates/complete-output.md.tmpl` and fill in `{version}`, `{count}` (phases, plans, commits), `{lines}`, `{duration}`.
 
 ---
 
@@ -536,7 +472,7 @@ Verify milestone completion with cross-phase integration checks.
 
    Display to the user: `◐ Spawning integration checker...`
 
-   Spawn `Task(agent_type: "pbr:integration-checker")`. Read `skills/milestone/templates/integration-checker-prompt.md.tmpl`, fill in `{version or "current"}`, `{list of phase directories}`, and `{phase SUMMARY.md paths}`, then use the filled template as the Task() prompt.
+   Spawn `Task(subagent_type: "pbr:integration-checker")`. Read `skills/milestone/templates/integration-checker-prompt.md.tmpl`, fill in `{version or "current"}`, `{list of phase directories}`, and `{phase SUMMARY.md paths}`, then use the filled template as the Task() prompt.
 
 4. **Check integration-checker completion:**
 
@@ -557,91 +493,7 @@ Verify milestone completion with cross-phase integration checks.
 
    **Spot-check:** After writing, verify `.planning/{version}-MILESTONE-AUDIT.md` exists on disk using Glob. If missing, re-attempt the write. If still missing, display an error and include findings inline.
 
-7. **Report to user** using branded banners:
-
-   **If PASSED:**
-   ```
-   ╔══════════════════════════════════════════════════════════════╗
-   ║  PLAN-BUILD-RUN ► MILESTONE AUDIT PASSED ✓                   ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   All phases verified, integration checks passed, requirements covered.
-
-
-
-   ╔══════════════════════════════════════════════════════════════╗
-   ║  ▶ NEXT UP                                                   ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   **Complete the milestone** — archive and tag
-
-   `/pbr:milestone complete {version}`
-
-   <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 ⚠             ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   Found {count} gaps:
-   - {gap 1}
-   - {gap 2}
-
-
-
-   ╔══════════════════════════════════════════════════════════════╗
-   ║  ▶ NEXT UP                                                   ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   **Close the gaps** — create fix phases
-
-   `/pbr:milestone gaps`
-
-   <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 ⚠              ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   Milestone functional but has {count} tech debt items.
-
-
-
-   ╔══════════════════════════════════════════════════════════════╗
-   ║  ▶ NEXT UP                                                   ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   **Address tech debt or proceed**
-
-   `/pbr:milestone gaps` — create cleanup phases
-   `/pbr:milestone complete` — proceed as-is
-
-   <sub>`/clear` first → fresh context window</sub>
-
-
-   ```
+7. **Report to user** using branded banners — read `skills/milestone/templates/audit-output.md.tmpl`. The template contains all 3 variants (PASSED, GAPS FOUND, TECH DEBT). Select the appropriate section based on audit result. Fill in `{version}`, `{count}`, `{gap 1}`, `{gap 2}` as applicable.
 
 ---
 
@@ -721,35 +573,7 @@ Create phases to close gaps found during an audit.
    docs(planning): add gap-closure phases from milestone audit
    ```
 
-9. **Confirm** with branded output:
-   ```
-   ╔══════════════════════════════════════════════════════════════╗
-   ║  PLAN-BUILD-RUN ► GAP PHASES CREATED ✓                       ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   Created {count} gap-closure phase(s):
-   - Phase {N}: {name}
-   - Phase {N+1}: {name}
-
-
-
-   ╔══════════════════════════════════════════════════════════════╗
-   ║  ▶ NEXT UP                                                   ║
-   ╚══════════════════════════════════════════════════════════════╝
-
-   **Plan the first gap-closure phase**
-
-   `/pbr:plan {N}`
-
-   <sub>`/clear` first → fresh context window</sub>
-
-
-
-   **Also available:**
-   - `/pbr:status` — see project status
-
-
-   ```
+9. **Confirm** with branded output — read `skills/milestone/templates/gaps-output.md.tmpl` and fill in `{count}` (gap-closure phases created), `{N}` (first gap phase number), `{name}` (phase name).
 
 ---
 

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

@@ -4,6 +4,8 @@ description: "Zero-friction idea capture. Append, list, or promote notes to todo
 argument-hint: "<text> | list | promote <index> [--global]"
 ---
 
+**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/cursor-pbr/skills/pause/SKILL.md

@@ -3,6 +3,8 @@ name: pause
 description: "Save your current session state for later resumption."
 ---
 
+**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:
@@ -181,6 +183,7 @@ Completed: {count} plans this session
 Remaining: {count} plans in this phase
 
 
+
 ╔══════════════════════════════════════════════════════════════╗
 ║  ▶ NEXT UP                                                   ║
 ╚══════════════════════════════════════════════════════════════╝
@@ -191,6 +194,7 @@ Remaining: {count} plans in this phase
 
 <sub>`/clear` first → fresh context window</sub>
 
+
 ```
 
 ---