Skip to main content
On this pageOverviewThe jobWhat's insideIntegrationsInstall · kr 2 700FAQBetter together
Workflow

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

Plan & Build researches the task, writes the plan, then builds it. A builder per task, a validator confirming each, nothing done without proof.

  • Research → plan → spec → build
  • Every task gated on evidence
  • Runs on your Claude key

kr 2 700one-time · lifetime updates · install →

/ 01 The job

What runs when you install the plugin.

Research becomes a plan, then a verifiable spec, then executed tasks.

  1. 01pre-plan researches across multiple rounds and writes a complete plan to plans/.
  2. 02plan-w-team turns the plan into an owner-assigned spec in specs/. It never builds.
  3. 03build runs a builder per task, each completing one task end-to-end.
  4. 04A validator independently checks each task against its acceptance criteria.
  5. 05doctor provisions the stack first — uv, optional Python, git.
/ 02 What's inside

Every artefact you're getting.

A plugin is a folder. Here's everything in it.

2 Agents

Domain experts, hot-loaded.

buildersonnet-4-5Completes one task and reports its evidence.
validatorsonnet-4-5Re-checks that task independently. Never self-report.

The whole plugin sits at ~/.claude/plugins/plan-and-build/. Every agent and hook is a file you can edit.

/ 03 Tools it reads + writes

Will it work with your stack?

Reads from
Your projectGit
Writes to
plans/specs/Your codebase
Requirements: Claude Code and git. uv is recommended — doctor installs it, and pulls ruff and ty on demand. The gates fail open without it.

Better with Core Methodology installed. Its disciplines are invoked when present, never re-bundled.

/ 04 Install & price

Four steps. From buy to first run.

Both commands arrive in your purchase email.

1Install Claude Code (Anthropic's free CLI). Already have it? Skip.
2Buy. We invite your GitHub account to the private repo. The marketplace itself is public.
3In Claude Code, run /plugin marketplace add TenkrAS/tenkr-plugin-marketplace to register the catalogue.
4Run /plugin install <plugin>@tenkr-plugin-marketplace. It clones from your private repo. Then type the plugin's command.
/ 05 Plugin-specific FAQ

What people ask before buying.

/ 01Do I need Core Methodology too?
No. It's a soft dependency — the commands degrade gracefully without it.
/ 02Does it touch my whole repo?
plans/ and specs/ are created on first use. Build tasks write wherever the spec says.
/ 03How is "evidence-gated" actually enforced?
By hooks. enforce-verification.py blocks task completion without proof at SubagentStop.