One skill, 22 commands, 5 loops, 14 deterministic gates. Every command below is a hire. Nothing to memorize: run the front door and every step ends with "done — next is X, want me to run it?"
/Krucible setup
THE IT GUY
Checks what you already have, sets up only what's missing — Notion, Codex — and hands you to the starting line.
/Krucible idea-blueprint YOU DECIDE
THE STRATEGIST
Human-in-the-loop ideation: three structured reviews pressure-test the idea before anything gets designed or built.
/Krucible blueprint-to-design YOU DECIDE
THE DESIGNER
Grows one clickable HTML prototype feature by feature, pausing after each so you react to something real.
/Krucible blueprint-to-architecture YOU DECIDE
THE ARCHITECT
Picks the stack with you — every option framed in cost, time, and maintenance terms a non-engineer owns comfortably.
/Krucible blueprint-to-user-stories
THE PM
Blueprint + designs become a tidy Notion backlog — a mandatory Setup card first, then one prefilled card per feature, MVP first.
/Krucible pitch
THE HYPE PERSON
A self-contained one-page demo styled to your product — show investors, iterate on it like everything else.
/Krucible feature-discovery
THE ANALYST
One question at a time, into the corners a tired human skips. The PRD that comes out is pseudocode for the build.
/Krucible design-review
THE UX LEAD
Reads the fresh PRD against the current design — "no change" is a valid verdict — and keeps the prototype current.
/Krucible technical-design
THE ENGINEER
PRD + design addendum become an implementation plan with diagrams — surfacing only the choices actually worth your time.
/Krucible develop
THE BUILDER
Implements exactly what the PRD + plan specify — and stops the moment it hits a real product decision the spec doesn't answer.
/Krucible code-review LOOP
THE SKEPTIC
A different model (Codex) reviews against the PRD. Issues route back to the builder; it re-reviews until a fresh pass finds zero blockers.
/Krucible test LOOP
THE QA LEAD
Every acceptance criterion executed against the running app — verified, never assumed — each mapped to pass/fail with evidence.
/Krucible sign-off YOU DECIDE
YOU
Walk each criterion in the app preview and give the verdict. On Accept it merges and points to the next story. It never merges without you.
/Krucible feedback LOOP
THE FIXER
"Change this" becomes tracked, resolved work — split into sub-features, each driven through its own review and sign-off.
/Krucible auto-build LOOP
THE AUTO-BUILDER
Runs the whole backlog story by story on its own — pausing only for real decisions and your sign-offs.
/Krucible final-review LOOP GATE
THE COMPLETENESS GATE
Checks the built MVP against everything the blueprint, architecture, and design promised — and re-runs until the verdict is Complete.
/Krucible security-review LOOP GATE
THE SECURITY OFFICER
An OWASP/STRIDE pass over the whole MVP. Every fix becomes a tracked card; launch stays locked until the verdict is Clean.
/Krucible launch GATE
THE RELEASE MANAGER
Hosting, env, domain, deploy, health checks — in plain cost and effort terms. Never touches your secrets or your money.
/Krucible document
THE TECHNICAL WRITER
README plus user and developer docs — grounded in what was actually built, not what was planned.
/Krucible post-launch-review
THE CHIEF OF STAFF
A short retro plus a prioritized "what's next" — deferred Later stories become the next build set, and the outer loop turns your MVP into v2.
/Krucible status
THE PROJECT MANAGER
Read-only, run anytime — where you are, what's done, what's parked, and the single next command. Your whole project in ten seconds.
/Krucible parking-lot
THE NOTE-KEEPER
Deferred decisions with their blast radius. Resolve one and the answer propagates to every doc and card it touches — nothing left inconsistent.
fig. 01 · the full roster — per-command deep dives in the second pass