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:

╔══════════════════════════════════════════════════════════════╗
║  PLAN-BUILD-RUN ► COMMAND REFERENCE                          ║
╚══════════════════════════════════════════════════════════════╝

Then proceed to Step 1.

/pbr:help — Plan-Build-Run Command Reference

Contextual Help

If $ARGUMENTS contains a command name (e.g., plan, build, review, config, quick), show detailed help for just that command instead of the full reference. Match the argument against the command tables below and display only the matching section with its subcommands and flags. If the argument doesn't match any command, show the full reference.

Examples:

• •/pbr:help plan → Show only the plan command and its flags (--assumptions, --skip-research, --gaps, add, insert, remove)
• •/pbr:help build → Show only the build command and its flags (--gaps-only, --team)
• •/pbr:help → Show the full reference below

Full Reference

Display the following reference to the user:

Plan-Build-Run Commands

Core Workflow (the main loop)

Planning & Discovery

Execution

Verification & Debugging

Session Management

Project Management

Analysis & Utilities

Choose Your Command

Not sure which command to use? Follow this guide:

Typical Workflow

/pbr:begin              ← Start project, define requirements, create roadmap
/pbr:discuss 1          ← (optional) Talk through phase details
/pbr:plan 1             ← Plan the first phase
/pbr:build 1            ← Build it
/pbr:review 1           ← Verify it works
/pbr:plan 2             ← Plan the next phase
...                     ← Repeat plan → build → review
/pbr:milestone complete ← Archive when done

Quick Reference

• •Context strategy: aggressive (delegate everything) | balanced | minimal (run inline)
• •Depth: quick (skip research, ~50% cheaper) | standard | comprehensive (~2x cost)
• •State files: .planning/STATE.md (position), .planning/ROADMAP.md (phases), .planning/config.json (settings)
• •Configure: /pbr:config to change depth, models, gates, parallelization
• •List agents: Run claude agents in your terminal to see all registered PBR agents and verify loading
• •Tip: Use /pbr:quick for creative/visual work where structured planning adds overhead without benefit.
• •PR hygiene: When creating PRs from a Plan-Build-Run project, .planning/ commits can be filtered using phase branching (git.branching: phase) which squash-merges code-only changes to main.
• •Seeds: /pbr:explore can create seed files (.planning/seeds/) with trigger conditions. Seeds auto-inject into planning when their trigger phase is reached.

Behavioral Contexts

Plan-Build-Run includes three behavioral contexts in contexts/ that adjust how Claude operates:

• •dev — Active development: write code first, low verbosity, medium risk tolerance
• •research — Exploration mode: read widely, no code writing, high verbosity, evidence-based
• •review — Code review: read thoroughly, prioritize by severity, report don't fix

Skills automatically activate the appropriate context: /pbr:build uses dev context, /pbr:discuss uses research context, /pbr:review uses review context.

When to Use Quick vs Plan+Build

Setup vs Begin

• •/pbr:begin — Use this to start a new project. It handles everything: questioning, research, requirements, roadmap, AND config initialization. This is the standard entry point.
• •/pbr:setup — Use this only to reconfigure an existing project's settings (model profiles, gates, depth, parallelization) without re-running the full begin flow.

If you're unsure, start with /pbr:begin. It will detect existing config and offer to reuse or overwrite.

Team Discussions

The features.team_discussions config flag (and /pbr:build --team) enables Agent Teams for complex builds. When enabled, executor agents can coordinate with each other during parallel wave execution — sharing context about what they've built, resolving interface conflicts, and avoiding duplicate work. Best for phases where multiple plans have shared dependencies. Configure via /pbr:config.

Getting Started

╔══════════════════════════════════════════════════════════════╗
║  ▶ 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

• •GitHub Issues: https://github.com/SienkLogic/plan-build-run/issues
• •README: https://github.com/SienkLogic/plan-build-run