architect

To convert a finalized spec into an implementation-ready architecture design, use a Socratic questioning workflow that guides interactive clarification, targeted codebase research, and iterative drafting to generate a concrete design document and ADRs.

Creating Architecture Decision Records from a project spec requires resolving gray areas through evidence-grounded research, combining codebase exploration with external references to ground architectural decisions before drafting the ADRs.

Yes, you need a finalized spec.md before starting architecture design. The workflow bridges the gap between finalized specs and build-ready architecture by ensuring all design decisions are grounded in answers from interactive clarification.

A Socratic workflow resolves architectural gray areas by asking targeted questions before drafting any design, ensuring you never write the architecture document without explicit answers that satisfy the architect Definition of Ready.

Yes, you can generate build-ready design documents alongside ADRs in one workflow. The phase-aligned process synthesizes intent capture, research, and gray-area resolution to output both design.md and ADRs while updating state.yaml.

A limitation of using a Socratic approach for architecture design is that it requires interactive questioning and explicit answers before drafting, meaning you cannot generate design documents autonomously without providing clarifying input.