agent-architect

To create a technical design plan without modifying your codebase, read the existing repository to identify patterns and constraints, then generate a deterministic plan covering design evaluation and implementation steps. This ensures all design choices are finalized before any file edits occur.

The best way to evaluate design approaches for a new feature is to analyze the existing codebase to surface constraints, then compare potential patterns to produce a concrete plan. This pre-implementation design phase highlights risks and choices early.

Yes, you can generate an actionable implementation plan without writing code by performing a read-only analysis of the codebase. The output is a deterministic plan with explicit execution steps that a worker can implement directly, ensuring no files are modified during the design phase.

No, pre-implementation design does not require modifying files during the planning phase. The process operates in a read-only mode to identify design constraints and patterns, producing a deterministic technical plan that defers all file writes and edits to the subsequent execution phase.

The main limitation of deterministic architectural planning is that it strictly defers all file modifications to the execution phase. While it successfully surfaces design choices and constraints early, the read-only planning process itself cannot directly apply codebase changes or perform edits.