Agile by construction. One story at a time — specced, built, reviewed, tested, accepted by you. Nothing ships past a gate — 14 deterministic checks, machine-read, no exceptions.
Guides your agents to ship a crafted product, not a frankenstein.
"Just ask AI to build my app" works right up until it doesn't. Unguided agents stitch together monsters. Krucible rebuilds the work like a product team would: specced, reviewed, tested, gated — not guesswork.
Works like a full product team.
22 commands, each one a hire — strategist to release manager, one product vocabulary. Pick a hire to watch them work, or browse the full reference →
The IT guy. Checks what you already have, sets up only what's missing — Notion, Codex — and hands you to the starting line.
A chief product officer's playbook, pre-installed in the pipeline.
You don't run these pages — the pipeline does. From naming the problem to measuring the outcome, every one is worked in order, on the record, so nothing gets skipped because nobody thought of it.
The pain, named in one sentence — before any solution gets airtime.
Who's already solving this — competitors, and benchmarks from other industries.
Your value proposition, why you'd still win, and how it will be priced.
Who the users are and what they need — personas, journeys, service blueprint, features.
Every feature a buildable story — MVP first, prioritized on purpose.
Cost, time, and maintenance weighed in plain terms before anything is committed.
"Done" written down before the work starts — binary, testable, never a feeling.
Success defined before launch, measured after. Output isn't the goal.
Already built with /Krucible.
Builders will say it better.
"I went from idea to live in six days without opening an IDE. Nine stories, every one signed off by me — the launch record reads like a flight log."
"I stopped re-explaining my product every session. The spec I approved in discovery is the spec that shipped, nine commands later."
"The security gate caught an unauthenticated cancel endpoint before launch. That one catch paid for the pizzas."
No learning curve. Just one command.
You don't memorize when to use what. Type the front door and Krucible reads your project state, tells you exactly where you are, and offers the one right next step. Finish it, and it offers the next. Keep saying yes.
→ "You're mid-build: story 4 of 9. Next is develop Search — want me to?"
Get started.
Free and open source (Apache 2.0). One paste to install, one command to set up. Runs inside your AI agent — on a Pro/Max-type plan, most usage comes out of your existing allowance.
/Krucible setup — it checks what you already have (Notion, Codex), fixes only what's missing, and offers the governance hook.
/Krucible idea-blueprint. From there the pipeline guides you — every step ends with the next one. Already have a backlog? Jump straight to /Krucible feature-discovery.
/Krucible status in a session, krucible check in CI. Update later with cd ~/.krucible && git pull && ./setup.
needs: git · an agent harness (Claude Code v2.0.21+ or Claude Cowork today — more soon) · Notion (the backlog) · OpenAI Codex (the second opinion)
Krucible, implemented for your platforms and products.
The engagement begins with a proof of concept: our forward deployed product manager delivers a real initiative on your own product, from idea to launch.
Every decision made by your team — nothing is assumed, nothing auto-accepted.
Complete documentation of every review, test, and sign-off.
We then embed with your teams through their first runs — until they build your products with Krucible independently.
The deliverables.
The discipline.