Plan complex work, then ship it with a team that proves every step.

What runs when you install the plugin.

Five commands, one pipeline. doctor provisions the stack first; then research becomes a plan, the plan becomes a verifiable spec, and the spec gets built — nothing marked done without proof.

1. 01pre-plan researches the task across multiple rounds and writes a complete implementation plan to plans/.
2. 02plan-w-team turns the plan into an owner-assigned, verifiable spec in specs/. Planning only — it never builds.
3. 03build deploys a builder per task and gates every task on verification evidence before it can be marked done.
4. 04A validator independently confirms each task against its acceptance criteria — independent evidence, not the builder's self-report.
5. 05doctor provisions the stack first — uv, optional Python, git — so the quality gates have what they need. The hooks fail open if uv is absent.

Every artefact you're getting.

A plugin is a folder. Here's everything in it — two agents, two skills, five commands, six hooks, and the plan template they all follow. The heaviest plugin in the catalogue, fully on show.

The whole plugin sits at ~/.claude/plugins/plan-and-build/ — every agent, every hook, and the plan template is a file you can read, edit, and version.

Will it work with your stack?

Better with Core Methodology installed — the commands invoke its disciplines (validation-first, verification-before-completion, deliverable-review) when present, and degrade gracefully when not. It does not re-bundle them.

Four steps. From buy to first run.

Buy on the right. On purchase, we invite your GitHub account to the private plugin repo you bought — the Tenkr marketplace itself is public — and email you the two commands below.

What people ask before buying.

The plugins people install with this one.