Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By SienkLogic
Execute Plan-Build-Run workflows in Claude Code to structure development: initialize projects with roadmaps, plan phases via subagent research and verification, build atomically with dependency waves and git commits, review against goals, debug systematically, generate tests, and manage persistent state across sessions.
npx claudepluginhub sienklogic/plan-build-runReview past Claude Code sessions for PBR workflow compliance and UX quality.
Start a new project. Deep questioning, research, requirements, and roadmap.
Execute all plans in a phase. Spawns agents to build in parallel, commits atomically.
Configure Plan-Build-Run settings. Model selection, workflow toggles, depth, gates, and parallelization.
Execute the next logical step automatically. No prompts, no decisions — just do it.
Analyzes Claude Code session logs for PBR workflow compliance, hook firing, state file hygiene, and user experience quality.
Explores existing codebases and writes structured analysis documents. Four focus areas: tech, arch, quality, concerns.
Systematic debugging using scientific method. Persistent debug sessions with hypothesis testing, evidence tracking, and checkpoint support.
Syncs PBR plugin changes to cursor-pbr and copilot-pbr derivatives with format adjustments.
Executes plan tasks with atomic commits, deviation handling, checkpoint protocols, TDD support, and self-verification.
Review past Claude Code sessions for PBR workflow compliance and UX quality.
Start a new project. Deep questioning, research, requirements, and roadmap.
Execute all plans in a phase. Spawns agents to build in parallel, commits atomically.
Configure settings: depth, model profiles, features, git, and gates.
Execute the next logical step automatically. No prompts, no decisions — just do it.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Conductor: Context-driven development for Claude Code - Measure twice, code once
Opinionated 5-phase development lifecycle for Claude Code — language-agnostic, repo-local bin/* delegation
Autonomous session orchestrator for Claude Code - manages multi-phase development workflows
End-to-end development workflow: design → draft-plan → orchestrate → review → pr-create → pr-review → pr-merge
Get Shit Done -- a structured workflow plugin for Claude Code that adds planning, execution, and verification commands with MCP-backed project state
Describe your goal, approve the spec, then step away — Claude and Codex loop together until it's right.
Modifies files
Hook triggers on file write and edit operations
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Context-engineered development workflow for Claude Code, Cursor, GitHub Copilot CLI, OpenAI Codex, and Google Jules.
Build ambitious multi-phase software without quality degradation.
Works with any Claude Code plan. Shines on Max. Now available for Cursor IDE and GitHub Copilot CLI.
Why Plan-Build-Run? •
Getting Started •
Commands •
How It Works •
Local LLM •
Wiki •
Contributing
Claude Code is remarkably capable...until your context window fills up. As tokens accumulate during a long session, reasoning quality degrades, hallucinations increase, and the model starts losing track of earlier decisions. This is context rot, and it's the primary failure mode when building anything beyond a single-session project.
Plan-Build-Run solves this. It keeps your main orchestrator under ~15% context usage by delegating heavy work to fresh subagent contexts, each getting a clean 200k token window. All state lives on disk. Sessions are killable at any second without data loss. Whether you're on a free tier or Max 5x, wasted context means wasted budget, and context rot is the biggest source of waste.
Most AI coding tools treat context as infinite. They index your codebase, track your edits, and hope the model keeps up. That works for single-file changes. It falls apart when you're building something that takes days, spans dozens of files, and requires decisions made on Monday to still hold on Friday.
Plan-Build-Run takes a different approach: structured context isolation. Instead of stuffing everything into one session, it delegates each operation to a fresh subagent with a clean 200k token window and coordinates through files on disk.
Goal-backward verification, lifecycle hooks, wave-based parallelism, kill-safe state, and local LLM offloading to cut frontier token costs on routine tasks. See What Sets It Apart for the full comparison and differentiators.
When to use Plan-Build-Run: Multi-phase projects where quality matters. New features spanning 5+ files, large refactors, greenfield builds, anything that would take more than one Claude Code session to complete. Use
depth: quickordepth: standardto control agent spawn count per phase.When to skip it: Single-file fixes, quick questions, one-off scripts. Use
/pbr:quickfor atomic commits without full workflow overhead: single executor spawn, no research or verification agents.
Works on every Claude Code plan. Use depth: quick on Free/Pro, depth: standard on Max, depth: comprehensive on Max 5x. See What Sets It Apart for tier-specific guidance.