Hainrixz/the-architect
A Claude Code plugin that interviews you, designs the whole architecture, and writes a self-contained blueprint another Claude Code instance builds from with zero context — EARS acceptance criteria and a runnable verify command on every build step. 14 project shapes, greenfield and brownfield. EN/ES.
What it solves
The Architect is a meta-agent for Claude Code that solves the problem of "hallucinated" or underspecified software plans. It prevents autonomous AI builders from making incorrect assumptions or over-building by creating a rigorous, detailed blueprint before any application code is written.
How it works
The tool operates through a four-phase design process:
- Discovery: Classifies the project into one of 14 "shapes" (e.g., SaaS, Agent App, CLI) and determines if it is new or existing code.
- Deep Dive: Uses a
stack-researchersubagent to verify library versions against live registries to ensure the stack is current. - Architecture: Defines the stack and scope, passing through two mandatory gates: Gate A (resolving all underspecified markers) and Gate B (an adversarial pre-mortem to identify risks).
- Generate: A
blueprint-writerandblueprint-validatorcreate and audit a markdown blueprint containing 20 fixed sections, including a strict build order with defined "Done when" and "Verify" criteria.
Who it’s for
It is designed for developers using Claude Code who want to hand off a project to an autonomous builder agent with minimal manual intervention, as well as those managing "brownfield" projects where changes must be integrated into an existing codebase.
Highlights
- Anti-Drift Build Steps: Every step includes specific
Do,Done when,Verify, andCheckpointfields to prevent agent drift. - EARS Acceptance Criteria: Uses the "Easy Approach to Requirements Syntax" (WHEN
THE SYSTEM SHALL ) to ensure all criteria are script-decidable. - Stack-Agnostic Shapes: 14 predefined project shapes that separate the "what" (shape) from the "how" (runtime track) and "capability."
- Brownfield Support: Includes a specialized flow to map existing repositories, respecting existing conventions and agent instructions.
- Live Registry Verification: Prevents stale dependencies by verifying version pins against authoritative registries during the design phase.
Related
- Project
- Project
- Project
- Project
- Project