A meta-agent that refuses to let your builder guess at 2am

What it does

It’s a Claude Code plugin that designs software instead of writing it. You describe the project, it interviews you (3 questions in quick mode, 12–16 in full mode), classifies it into one of 14 project shapes, and emits a markdown blueprint with 20 fixed sections. A different Claude Code instance — with no prior context — then builds from that blueprint without asking you anything.

The interesting bit

The discipline is the product. Every build step carries four fields: Do, Done when, Verify, Checkpoint. Acceptance criteria must be in EARS form (WHEN <trigger> THE SYSTEM SHALL <observable response>) and decidable by a script today — “billing works” is literally banned, and a validator fails blueprints containing it. Two gates block generation: one that scans for unresolved decisions (no [NEEDS CLARIFICATION] markers survive), and an adversarial pre-mortem that tries to kill the plan across eight angles before it ships.

Key highlights

• 14 stack-agnostic project shapes, covering greenfield and brownfield, from SaaS webapps to mobile to internal tools
• Two entry points: /architect-quick (~10 min) and /architect (~40–60 min) — both keep the gates and EARS criteria
• A stack-researcher subagent verifies every pinned version against live registries
• Output is a bundle (12+ steps, with a task DAG and a copy-in workspace/ of agent config) or a single file (11 or fewer) — it picks and tells you which
• Bilingual: full English and Spanish READMEs

Caveats

• Generation is slow and silent: 20–30 minutes for a bundle with no output until done (the README insists the tool must warn you first)
• Requires a Claude Code subscription; the slash commands and subagents are plugin-only — clone mode runs the same flow conversationally
• The pre-mortem’s /abogado-del-diablo integration is optional tooling; the gate runs inline otherwise

Verdict

Worth a look if you hand projects to autonomous builders and want a stopping condition per step instead of vibes-based “done.” If you want a tool that writes application code, this explicitly isn’t it — it’s the plan, not the hammer.