@sienklogic/plan-build-run 2.22.0 → 2.22.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (52) hide show
  1. package/CHANGELOG.md +7 -0
  2. package/package.json +1 -1
  3. package/plugins/copilot-pbr/hooks/hooks.json +0 -12
  4. package/plugins/copilot-pbr/plugin.json +1 -1
  5. package/plugins/copilot-pbr/skills/begin/SKILL.md +2 -41
  6. package/plugins/copilot-pbr/skills/build/SKILL.md +4 -84
  7. package/plugins/copilot-pbr/skills/config/SKILL.md +1 -1
  8. package/plugins/copilot-pbr/skills/help/SKILL.md +17 -0
  9. package/plugins/copilot-pbr/skills/review/SKILL.md +4 -96
  10. package/plugins/cursor-pbr/.cursor-plugin/plugin.json +1 -1
  11. package/plugins/cursor-pbr/hooks/hooks.json +0 -10
  12. package/plugins/cursor-pbr/skills/begin/SKILL.md +2 -41
  13. package/plugins/cursor-pbr/skills/build/SKILL.md +4 -84
  14. package/plugins/cursor-pbr/skills/config/SKILL.md +1 -1
  15. package/plugins/cursor-pbr/skills/help/SKILL.md +17 -0
  16. package/plugins/cursor-pbr/skills/review/SKILL.md +4 -96
  17. package/plugins/pbr/.claude-plugin/plugin.json +1 -1
  18. package/plugins/pbr/hooks/hooks.json +0 -10
  19. package/plugins/pbr/scripts/check-cross-plugin-sync.js +1 -1
  20. package/plugins/pbr/scripts/check-phase-boundary.js +2 -2
  21. package/plugins/pbr/scripts/check-roadmap-sync.js +1 -1
  22. package/plugins/pbr/scripts/check-subagent-output.js +1 -1
  23. package/plugins/pbr/scripts/log-tool-failure.js +1 -1
  24. package/plugins/pbr/scripts/post-write-dispatch.js +8 -0
  25. package/plugins/pbr/scripts/pre-bash-dispatch.js +2 -2
  26. package/plugins/pbr/scripts/validate-task.js +1 -1
  27. package/plugins/pbr/skills/begin/SKILL.md +2 -44
  28. package/plugins/pbr/skills/build/SKILL.md +4 -99
  29. package/plugins/pbr/skills/config/SKILL.md +1 -1
  30. package/plugins/pbr/skills/help/SKILL.md +17 -0
  31. package/plugins/pbr/skills/review/SKILL.md +4 -102
  32. package/plugins/copilot-pbr/references/agent-interactions.md +0 -135
  33. package/plugins/copilot-pbr/references/planning-config.md +0 -214
  34. package/plugins/copilot-pbr/references/subagent-coordination.md +0 -120
  35. package/plugins/copilot-pbr/skills/shared/error-recovery-strategies.md +0 -51
  36. package/plugins/copilot-pbr/skills/shared/error-reporting.md +0 -81
  37. package/plugins/copilot-pbr/skills/shared/progress-display.md +0 -53
  38. package/plugins/copilot-pbr/skills/shared/state-loading.md +0 -63
  39. package/plugins/cursor-pbr/references/agent-interactions.md +0 -135
  40. package/plugins/cursor-pbr/references/planning-config.md +0 -214
  41. package/plugins/cursor-pbr/references/subagent-coordination.md +0 -120
  42. package/plugins/cursor-pbr/skills/shared/error-recovery-strategies.md +0 -51
  43. package/plugins/cursor-pbr/skills/shared/error-reporting.md +0 -81
  44. package/plugins/cursor-pbr/skills/shared/progress-display.md +0 -53
  45. package/plugins/cursor-pbr/skills/shared/state-loading.md +0 -63
  46. package/plugins/pbr/references/agent-interactions.md +0 -134
  47. package/plugins/pbr/references/planning-config.md +0 -213
  48. package/plugins/pbr/references/subagent-coordination.md +0 -119
  49. package/plugins/pbr/skills/shared/error-recovery-strategies.md +0 -51
  50. package/plugins/pbr/skills/shared/error-reporting.md +0 -81
  51. package/plugins/pbr/skills/shared/progress-display.md +0 -53
  52. package/plugins/pbr/skills/shared/state-loading.md +0 -62
package/CHANGELOG.md CHANGED
@@ -5,6 +5,13 @@ All notable changes to Plan-Build-Run will be documented in this file.
5
5
  The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
  and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
 
8
+ ## [2.22.1](https://github.com/SienkLogic/plan-build-run/compare/plan-build-run-v2.22.0...plan-build-run-v2.22.1) (2026-02-24)
9
+
10
+
11
+ ### Bug Fixes
12
+
13
+ * **tools:** standardize error messages with severity prefix and actionable next-steps ([3b3b6dd](https://github.com/SienkLogic/plan-build-run/commit/3b3b6dd2cd1d868896edccfec19acefcb70b087f))
14
+
8
15
  ## [2.22.0](https://github.com/SienkLogic/plan-build-run/compare/plan-build-run-v2.21.1...plan-build-run-v2.22.0) (2026-02-23)
9
16
 
10
17
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sienklogic/plan-build-run",
3
- "version": "2.22.0",
3
+ "version": "2.22.1",
4
4
  "description": "Plan it, Build it, Run it — structured development workflow for Claude Code",
5
5
  "keywords": [
6
6
  "claude-code",
@@ -28,18 +28,6 @@
28
28
  }
29
29
  ]
30
30
  },
31
- {
32
- "matcher": "Write|Edit",
33
- "hooks": [
34
- {
35
- "type": "command",
36
- "bash": "node \"$(cd \"$(dirname \"$0\")\" && pwd)/../../pbr/scripts/run-hook.js\" post-write-quality.js",
37
- "powershell": "node (Join-Path (Split-Path -Parent $PSScriptRoot) 'pbr\\scripts\\run-hook.js') post-write-quality.js",
38
- "cwd": ".",
39
- "timeoutSec": 15
40
- }
41
- ]
42
- },
43
31
  {
44
32
  "matcher": "Task",
45
33
  "hooks": [
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "pbr",
3
3
  "displayName": "Plan-Build-Run",
4
- "version": "2.22.0",
4
+ "version": "2.22.1",
5
5
  "description": "Plan-Build-Run — Structured development workflow for GitHub Copilot CLI. Solves context rot through disciplined agent delegation, structured planning, atomic execution, and goal-backward verification.",
6
6
  "author": {
7
7
  "name": "SienkLogic",
@@ -503,48 +503,9 @@ Delete `.planning/.active-skill` if it exists. This must happen on all paths (su
503
503
 
504
504
  ## Completion
505
505
 
506
- After all steps complete, present the final summary:
506
+ After all steps complete, present the final summary using the stage banner format from Read `references/ui-formatting.md`:
507
507
 
508
- Use the branded stage banner from `references/ui-formatting.md`:
509
-
510
- ```
511
- ╔══════════════════════════════════════════════════════════════╗
512
- ║ PLAN-BUILD-RUN ► PROJECT INITIALIZED ║
513
- ╚══════════════════════════════════════════════════════════════╝
514
-
515
- **{name}**
516
-
517
- {core value one-liner}
518
-
519
- Roadmap: {N} phases
520
- 1. {Phase 1 name}
521
- 2. {Phase 2 name}
522
- ...
523
-
524
- Requirements: {N} committed, {M} deferred, {K} out-of-scope
525
- ```
526
-
527
- Then use the "Next Up" routing block:
528
- ```
529
- ---
530
-
531
- ## Next Up
532
-
533
- **Phase 1: {Name}** — {one-line goal}
534
-
535
- `/pbr:discuss 1`
536
-
537
- `/clear` first for a fresh context window
538
-
539
- ---
540
-
541
- **Also available:**
542
- - `/pbr:explore` — open-ended exploration before planning
543
- - `/pbr:plan 1` — jump straight to planning Phase 1
544
- - `/pbr:config` — adjust workflow settings
545
-
546
- ---
547
- ```
508
+ Display the `PROJECT INITIALIZED` banner with project name, core value, phase list, and requirement counts. Then display the "Next Up" block (see § "Next Up Block" in ui-formatting.md) pointing to `/pbr:discuss 1` with alternatives: `/pbr:explore`, `/pbr:plan 1`, `/pbr:config`.
548
509
 
549
510
  ---
550
511
 
@@ -807,91 +807,11 @@ Total files modified: {count}
807
807
  Deviations: {count}
808
808
  ```
809
809
 
810
- Then present the appropriate branded banner:
810
+ Then present the appropriate branded banner from Read `references/ui-formatting.md` § "Completion Summary Templates":
811
811
 
812
- **If `passed` + more phases:**
813
- ```
814
- ╔══════════════════════════════════════════════════════════════╗
815
- ║ PLAN-BUILD-RUN ► PHASE {N} COMPLETE ✓ ║
816
- ╚══════════════════════════════════════════════════════════════╝
817
-
818
- **Phase {N}: {Name}**
819
-
820
- {X} plans executed
821
- Goal verified ✓
822
-
823
- ╔══════════════════════════════════════════════════════════════╗
824
- ║ ▶ NEXT UP ║
825
- ╚══════════════════════════════════════════════════════════════╝
826
-
827
- **Phase {N+1}: {Name}** — {Goal from ROADMAP.md}
828
-
829
- `/pbr:plan {N+1}`
830
-
831
- <sub>`/clear` first → fresh context window</sub>
832
-
833
- **Also available:**
834
- - `/pbr:review {N}` — manual acceptance testing before continuing
835
- - `/pbr:discuss {N+1}` — talk through the next phase before planning
836
- - `/pbr:status` — see full project status
837
-
838
- ```
839
-
840
- **If `passed` + last phase:**
841
- ```
842
- ╔══════════════════════════════════════════════════════════════╗
843
- ║ PLAN-BUILD-RUN ► MILESTONE COMPLETE 🎉 ║
844
- ╚══════════════════════════════════════════════════════════════╝
845
-
846
- {N} phases completed
847
- All phase goals verified ✓
848
-
849
- ╔══════════════════════════════════════════════════════════════╗
850
- ║ ▶ NEXT UP ║
851
- ╚══════════════════════════════════════════════════════════════╝
852
-
853
- **Audit milestone** — verify requirements, cross-phase integration, E2E flows
854
-
855
- `/pbr:milestone audit`
856
-
857
- <sub>`/clear` first → fresh context window</sub>
858
-
859
- **Also available:**
860
- - `/pbr:review` — manual acceptance testing
861
- - `/pbr:milestone complete` — archive milestone after audit passes
862
-
863
- ```
864
-
865
- **If `gaps_found`:**
866
- ```
867
- ╔══════════════════════════════════════════════════════════════╗
868
- ║ PLAN-BUILD-RUN ► PHASE {N} GAPS FOUND ⚠ ║
869
- ╚══════════════════════════════════════════════════════════════╝
870
-
871
- **Phase {N}: {Name}**
872
-
873
- Score: {X}/{Y} must-haves verified
874
- Report: .planning/phases/{phase_dir}/VERIFICATION.md
875
-
876
- ### What's Missing
877
-
878
- {Extract gap summaries from VERIFICATION.md}
879
-
880
- ╔══════════════════════════════════════════════════════════════╗
881
- ║ ▶ NEXT UP ║
882
- ╚══════════════════════════════════════════════════════════════╝
883
-
884
- **Plan gap closure** — create additional plans to complete the phase
885
-
886
- `/pbr:plan {N} --gaps`
887
-
888
- <sub>`/clear` first → fresh context window</sub>
889
-
890
- **Also available:**
891
- - `cat .planning/phases/{phase_dir}/VERIFICATION.md` — see full report
892
- - `/pbr:review {N}` — manual testing before planning
893
-
894
- ```
812
+ - **If `passed` + more phases:** Use the "Phase Complete" template. Fill in phase number, name, plan count, and next phase details.
813
+ - **If `passed` + last phase:** Use the "Milestone Complete" template. Fill in phase count.
814
+ - **If `gaps_found`:** Use the "Gaps Found" template. Fill in phase number, name, score, and gap summaries from VERIFICATION.md.
895
815
 
896
816
  **8g. Display USER-SETUP.md (conditional):**
897
817
 
@@ -23,7 +23,7 @@ Reads and writes `.planning/config.json`. Interactive configuration with AskUser
23
23
 
24
24
  ## References
25
25
 
26
- - `references/planning-config.md` — Full config.json schema (54 fields, 16 feature toggles, validation rules)
26
+ - `references/config-reference.md` — Full config.json schema (54 fields, 16 feature toggles, validation rules)
27
27
  - `references/model-profiles.md` — Model selection guide for agent spawning
28
28
 
29
29
  ## Flow
@@ -117,6 +117,23 @@ Display the following reference to the user:
117
117
  | `/pbr:dashboard --port <N>` | Launch dashboard on a specific port. |
118
118
  | `/pbr:statusline` | Install or configure the PBR status line in Claude Code. |
119
119
 
120
+ ## Choose Your Command
121
+
122
+ Not sure which command to use? Follow this guide:
123
+
124
+ | I want to... | Command |
125
+ |--------------|---------|
126
+ | Start a new project | `/pbr:begin` |
127
+ | Fix a bug or investigate an error | `/pbr:debug` |
128
+ | Think through an idea or approach | `/pbr:explore` |
129
+ | Do a small task (≤3 files) | `/pbr:quick` |
130
+ | Plan a complex change (4+ files) | `/pbr:plan <N>` |
131
+ | See where I am and what's next | `/pbr:status` |
132
+ | Auto-execute the next step | `/pbr:continue` |
133
+ | Describe something and let PBR route it | `/pbr:do <description>` |
134
+ | Lock decisions for a specific phase | `/pbr:discuss <N>` |
135
+ | Check project health | `/pbr:health` |
136
+
120
137
  ## Typical Workflow
121
138
 
122
139
  ```
@@ -542,103 +542,11 @@ Delete `.planning/.active-skill` if it exists. This must happen on all paths (su
542
542
 
543
543
  ## Completion
544
544
 
545
- After review completes, always present a clear next action:
545
+ After review completes, always present a clear next action using the completion banners from Read `references/ui-formatting.md` § "Completion Summary Templates":
546
546
 
547
- **If verified (not final phase):**
548
-
549
- Display the "Phase Complete" banner inline:
550
- ```
551
- ╔══════════════════════════════════════════════════════════════╗
552
- ║ PLAN-BUILD-RUN ► PHASE {N} COMPLETE ║
553
- ╚══════════════════════════════════════════════════════════════╝
554
-
555
- **Phase {N}: {Name}**
556
-
557
- {X} plans executed
558
- Goal verified
559
- ```
560
-
561
- Then the branded "Next Up" block:
562
- ```
563
- ---
564
-
565
- ## Next Up
566
-
567
- **Phase {N+1}: {Name}** — {Goal from ROADMAP.md}
568
-
569
- `/pbr:plan {N+1}`
570
-
571
- `/clear` first for a fresh context window
572
-
573
- ---
574
-
575
- **Also available:**
576
- - `/pbr:discuss {N+1}` — talk through details before planning
577
- - `/pbr:status` — see full project status
578
-
579
- ---
580
- ```
581
-
582
- **If gaps remain:**
583
- ```
584
- ╔══════════════════════════════════════════════════════════════╗
585
- ║ PLAN-BUILD-RUN ► PHASE {N} GAPS FOUND ║
586
- ╚══════════════════════════════════════════════════════════════╝
587
-
588
- **Phase {N}: {name}** — {count} gaps remaining
589
-
590
- ---
591
-
592
- ## Next Up
593
-
594
- **Fix gaps** — diagnose and create fix plans
595
-
596
- `/pbr:review {N} --auto-fix`
597
-
598
- `/clear` first for a fresh context window
599
-
600
- ---
601
-
602
- **Also available:**
603
- - `/pbr:plan {N} --gaps` — create fix plans manually
604
- - Fix manually, then `/pbr:review {N}`
605
-
606
- ---
607
- ```
608
-
609
- **If final phase:**
610
-
611
- Display the "Milestone Complete" banner inline:
612
- ```
613
- ╔══════════════════════════════════════════════════════════════╗
614
- ║ PLAN-BUILD-RUN ► MILESTONE COMPLETE ║
615
- ╚══════════════════════════════════════════════════════════════╝
616
-
617
- {N} phases completed
618
- All phase goals verified
619
- ```
620
-
621
- Then:
622
- ```
623
- ---
624
-
625
- ## Next Up
626
-
627
- **Audit milestone** — verify cross-phase integration
628
-
629
- `/pbr:milestone audit`
630
-
631
- `/clear` first for a fresh context window
632
-
633
- ---
634
-
635
- **Also available:**
636
- - `/pbr:milestone complete` — archive this milestone and tag it
637
- - `/pbr:milestone new` — start planning next features
638
- - `/pbr:status` — see final project status
639
-
640
- ---
641
- ```
547
+ - **If verified (not final phase):** Use the "Phase Complete" template. Fill in phase number, name, plan count, and next phase details.
548
+ - **If gaps remain:** Use the "Gaps Found" template. Fill in phase number, name, gap count, and gap summaries.
549
+ - **If final phase:** Use the "Milestone Complete" template. Fill in phase count.
642
550
 
643
551
  ---
644
552
 
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "pbr",
3
3
  "displayName": "Plan-Build-Run",
4
- "version": "2.22.0",
4
+ "version": "2.22.1",
5
5
  "description": "Plan-Build-Run — Structured development workflow for Cursor. Solves context rot through disciplined subagent delegation, structured planning, atomic execution, and goal-backward verification.",
6
6
  "author": {
7
7
  "name": "SienkLogic",
@@ -24,16 +24,6 @@
24
24
  }
25
25
  ]
26
26
  },
27
- {
28
- "matcher": "Write|Edit",
29
- "hooks": [
30
- {
31
- "type": "command",
32
- "command": "node -e \"var r=process.env.CLAUDE_PLUGIN_ROOT||'',m=r.match(/^\\/([a-zA-Z])\\/(.*)/);if(m)r=m[1]+String.fromCharCode(58)+String.fromCharCode(92)+m[2];require(require('path').resolve(r,'..','pbr','scripts','run-hook.js'))\" post-write-quality.js",
33
- "statusMessage": "Running quality checks..."
34
- }
35
- ]
36
- },
37
27
  {
38
28
  "matcher": "Task",
39
29
  "hooks": [
@@ -503,48 +503,9 @@ Delete `.planning/.active-skill` if it exists. This must happen on all paths (su
503
503
 
504
504
  ## Completion
505
505
 
506
- After all steps complete, present the final summary:
506
+ After all steps complete, present the final summary using the stage banner format from Read `references/ui-formatting.md`:
507
507
 
508
- Use the branded stage banner from `references/ui-formatting.md`:
509
-
510
- ```
511
- ╔══════════════════════════════════════════════════════════════╗
512
- ║ PLAN-BUILD-RUN ► PROJECT INITIALIZED ║
513
- ╚══════════════════════════════════════════════════════════════╝
514
-
515
- **{name}**
516
-
517
- {core value one-liner}
518
-
519
- Roadmap: {N} phases
520
- 1. {Phase 1 name}
521
- 2. {Phase 2 name}
522
- ...
523
-
524
- Requirements: {N} committed, {M} deferred, {K} out-of-scope
525
- ```
526
-
527
- Then use the "Next Up" routing block:
528
- ```
529
- ---
530
-
531
- ## Next Up
532
-
533
- **Phase 1: {Name}** — {one-line goal}
534
-
535
- `/pbr:discuss 1`
536
-
537
- `/clear` first for a fresh context window
538
-
539
- ---
540
-
541
- **Also available:**
542
- - `/pbr:explore` — open-ended exploration before planning
543
- - `/pbr:plan 1` — jump straight to planning Phase 1
544
- - `/pbr:config` — adjust workflow settings
545
-
546
- ---
547
- ```
508
+ Display the `PROJECT INITIALIZED` banner with project name, core value, phase list, and requirement counts. Then display the "Next Up" block (see § "Next Up Block" in ui-formatting.md) pointing to `/pbr:discuss 1` with alternatives: `/pbr:explore`, `/pbr:plan 1`, `/pbr:config`.
548
509
 
549
510
  ---
550
511
 
@@ -808,91 +808,11 @@ Total files modified: {count}
808
808
  Deviations: {count}
809
809
  ```
810
810
 
811
- Then present the appropriate branded banner:
811
+ Then present the appropriate branded banner from Read `references/ui-formatting.md` § "Completion Summary Templates":
812
812
 
813
- **If `passed` + more phases:**
814
- ```
815
- ╔══════════════════════════════════════════════════════════════╗
816
- ║ PLAN-BUILD-RUN ► PHASE {N} COMPLETE ✓ ║
817
- ╚══════════════════════════════════════════════════════════════╝
818
-
819
- **Phase {N}: {Name}**
820
-
821
- {X} plans executed
822
- Goal verified ✓
823
-
824
- ╔══════════════════════════════════════════════════════════════╗
825
- ║ ▶ NEXT UP ║
826
- ╚══════════════════════════════════════════════════════════════╝
827
-
828
- **Phase {N+1}: {Name}** — {Goal from ROADMAP.md}
829
-
830
- `/pbr:plan {N+1}`
831
-
832
- <sub>`/clear` first → fresh context window</sub>
833
-
834
- **Also available:**
835
- - `/pbr:review {N}` — manual acceptance testing before continuing
836
- - `/pbr:discuss {N+1}` — talk through the next phase before planning
837
- - `/pbr:status` — see full project status
838
-
839
- ```
840
-
841
- **If `passed` + last phase:**
842
- ```
843
- ╔══════════════════════════════════════════════════════════════╗
844
- ║ PLAN-BUILD-RUN ► MILESTONE COMPLETE 🎉 ║
845
- ╚══════════════════════════════════════════════════════════════╝
846
-
847
- {N} phases completed
848
- All phase goals verified ✓
849
-
850
- ╔══════════════════════════════════════════════════════════════╗
851
- ║ ▶ NEXT UP ║
852
- ╚══════════════════════════════════════════════════════════════╝
853
-
854
- **Audit milestone** — verify requirements, cross-phase integration, E2E flows
855
-
856
- `/pbr:milestone audit`
857
-
858
- <sub>`/clear` first → fresh context window</sub>
859
-
860
- **Also available:**
861
- - `/pbr:review` — manual acceptance testing
862
- - `/pbr:milestone complete` — archive milestone after audit passes
863
-
864
- ```
865
-
866
- **If `gaps_found`:**
867
- ```
868
- ╔══════════════════════════════════════════════════════════════╗
869
- ║ PLAN-BUILD-RUN ► PHASE {N} GAPS FOUND ⚠ ║
870
- ╚══════════════════════════════════════════════════════════════╝
871
-
872
- **Phase {N}: {Name}**
873
-
874
- Score: {X}/{Y} must-haves verified
875
- Report: .planning/phases/{phase_dir}/VERIFICATION.md
876
-
877
- ### What's Missing
878
-
879
- {Extract gap summaries from VERIFICATION.md}
880
-
881
- ╔══════════════════════════════════════════════════════════════╗
882
- ║ ▶ NEXT UP ║
883
- ╚══════════════════════════════════════════════════════════════╝
884
-
885
- **Plan gap closure** — create additional plans to complete the phase
886
-
887
- `/pbr:plan {N} --gaps`
888
-
889
- <sub>`/clear` first → fresh context window</sub>
890
-
891
- **Also available:**
892
- - `cat .planning/phases/{phase_dir}/VERIFICATION.md` — see full report
893
- - `/pbr:review {N}` — manual testing before planning
894
-
895
- ```
813
+ - **If `passed` + more phases:** Use the "Phase Complete" template. Fill in phase number, name, plan count, and next phase details.
814
+ - **If `passed` + last phase:** Use the "Milestone Complete" template. Fill in phase count.
815
+ - **If `gaps_found`:** Use the "Gaps Found" template. Fill in phase number, name, score, and gap summaries from VERIFICATION.md.
896
816
 
897
817
  **8g. Display USER-SETUP.md (conditional):**
898
818
 
@@ -23,7 +23,7 @@ Reads and writes `.planning/config.json`. Interactive configuration with AskUser
23
23
 
24
24
  ## References
25
25
 
26
- - `references/planning-config.md` — Full config.json schema (54 fields, 16 feature toggles, validation rules)
26
+ - `references/config-reference.md` — Full config.json schema (54 fields, 16 feature toggles, validation rules)
27
27
  - `references/model-profiles.md` — Model selection guide for agent spawning
28
28
 
29
29
  ## Flow
@@ -117,6 +117,23 @@ Display the following reference to the user:
117
117
  | `/pbr:dashboard --port <N>` | Launch dashboard on a specific port. |
118
118
  | `/pbr:statusline` | Install or configure the PBR status line in Claude Code. |
119
119
 
120
+ ## Choose Your Command
121
+
122
+ Not sure which command to use? Follow this guide:
123
+
124
+ | I want to... | Command |
125
+ |--------------|---------|
126
+ | Start a new project | `/pbr:begin` |
127
+ | Fix a bug or investigate an error | `/pbr:debug` |
128
+ | Think through an idea or approach | `/pbr:explore` |
129
+ | Do a small task (≤3 files) | `/pbr:quick` |
130
+ | Plan a complex change (4+ files) | `/pbr:plan <N>` |
131
+ | See where I am and what's next | `/pbr:status` |
132
+ | Auto-execute the next step | `/pbr:continue` |
133
+ | Describe something and let PBR route it | `/pbr:do <description>` |
134
+ | Lock decisions for a specific phase | `/pbr:discuss <N>` |
135
+ | Check project health | `/pbr:health` |
136
+
120
137
  ## Typical Workflow
121
138
 
122
139
  ```
@@ -543,103 +543,11 @@ Delete `.planning/.active-skill` if it exists. This must happen on all paths (su
543
543
 
544
544
  ## Completion
545
545
 
546
- After review completes, always present a clear next action:
546
+ After review completes, always present a clear next action using the completion banners from Read `references/ui-formatting.md` § "Completion Summary Templates":
547
547
 
548
- **If verified (not final phase):**
549
-
550
- Display the "Phase Complete" banner inline:
551
- ```
552
- ╔══════════════════════════════════════════════════════════════╗
553
- ║ PLAN-BUILD-RUN ► PHASE {N} COMPLETE ║
554
- ╚══════════════════════════════════════════════════════════════╝
555
-
556
- **Phase {N}: {Name}**
557
-
558
- {X} plans executed
559
- Goal verified
560
- ```
561
-
562
- Then the branded "Next Up" block:
563
- ```
564
- ---
565
-
566
- ## Next Up
567
-
568
- **Phase {N+1}: {Name}** — {Goal from ROADMAP.md}
569
-
570
- `/pbr:plan {N+1}`
571
-
572
- `/clear` first for a fresh context window
573
-
574
- ---
575
-
576
- **Also available:**
577
- - `/pbr:discuss {N+1}` — talk through details before planning
578
- - `/pbr:status` — see full project status
579
-
580
- ---
581
- ```
582
-
583
- **If gaps remain:**
584
- ```
585
- ╔══════════════════════════════════════════════════════════════╗
586
- ║ PLAN-BUILD-RUN ► PHASE {N} GAPS FOUND ║
587
- ╚══════════════════════════════════════════════════════════════╝
588
-
589
- **Phase {N}: {name}** — {count} gaps remaining
590
-
591
- ---
592
-
593
- ## Next Up
594
-
595
- **Fix gaps** — diagnose and create fix plans
596
-
597
- `/pbr:review {N} --auto-fix`
598
-
599
- `/clear` first for a fresh context window
600
-
601
- ---
602
-
603
- **Also available:**
604
- - `/pbr:plan {N} --gaps` — create fix plans manually
605
- - Fix manually, then `/pbr:review {N}`
606
-
607
- ---
608
- ```
609
-
610
- **If final phase:**
611
-
612
- Display the "Milestone Complete" banner inline:
613
- ```
614
- ╔══════════════════════════════════════════════════════════════╗
615
- ║ PLAN-BUILD-RUN ► MILESTONE COMPLETE ║
616
- ╚══════════════════════════════════════════════════════════════╝
617
-
618
- {N} phases completed
619
- All phase goals verified
620
- ```
621
-
622
- Then:
623
- ```
624
- ---
625
-
626
- ## Next Up
627
-
628
- **Audit milestone** — verify cross-phase integration
629
-
630
- `/pbr:milestone audit`
631
-
632
- `/clear` first for a fresh context window
633
-
634
- ---
635
-
636
- **Also available:**
637
- - `/pbr:milestone complete` — archive this milestone and tag it
638
- - `/pbr:milestone new` — start planning next features
639
- - `/pbr:status` — see final project status
640
-
641
- ---
642
- ```
548
+ - **If verified (not final phase):** Use the "Phase Complete" template. Fill in phase number, name, plan count, and next phase details.
549
+ - **If gaps remain:** Use the "Gaps Found" template. Fill in phase number, name, gap count, and gap summaries.
550
+ - **If final phase:** Use the "Milestone Complete" template. Fill in phase count.
643
551
 
644
552
  ---
645
553
 
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pbr",
3
- "version": "2.22.0",
3
+ "version": "2.22.1",
4
4
  "description": "Plan-Build-Run — Structured development workflow for Claude Code. Solves context rot through disciplined subagent delegation, structured planning, atomic execution, and goal-backward verification.",
5
5
  "author": {
6
6
  "name": "SienkLogic",