meta-architect

Use when the user wants architecture-first product and system design with explicit stack rationale, boundaries, tradeoffs, data model choices, and phased delivery planning.

Use when the user wants to decide whether implementation is ready, what remains blocked, and what the exact next build step should be.

Use when the user wants logic validation: states, transitions, invariants, edge cases, dead ends, and blockers before implementation.

Use when the user wants evidence-backed technology choices, OSS evaluation, and source-grounded validation of the stack proposed in `$arch`.

Use when the user wants a security and trust-boundary review of the current design before implementation or release.

Use when the user wants a DX and UX review of the planned workflow before implementation proceeds.

Use when the user needs scope alignment, shared language, or docs clarity before or between gated lanes.

Use when the user wants contract-preserving simplification, anti-slop cleanup, or a final-pass polish after the main decision is made.

Use when the user needs failure triage, blocked-lane diagnosis, or root-cause decomposition before the next gate can move.

Use when the user wants the singular Meta-Architect in-session autonomous manager: choose the best next workflow step, manage the fixed gated workflow, and route bounded helper handoffs inside Codex.

Use when the user wants regression-first or test-first scaffolding before implementation work expands.