visual-architect

Visual architecture planning renders software specifications into a machine-readable implementation plan and a companion HTML document with architecture diagrams. This makes dependencies, risks, and execution sequences easier to validate before coding begins.

Generating implementation plans from an existing codebase requires read-only codebase investigation to map specifications to exact files, dependencies, tests, and integration points. The process yields a structured plan.md artifact for downstream engineering and audit workflows.

You can include Mermaid diagrams in your HTML architecture review document through explicit Mermaid source fallbacks. This ensures architecture diagrams, schema views, and wireframes render correctly within synchronized HTML output for human review.

Visual planning for feature development supports API design, schema mapping, and risk validation within structured milestone workflows. It produces annotated code and API contracts inside a visual review document to ground architecture planning in codebase realities.

A synchronized HTML output is needed alongside your implementation plan to provide a self-contained visual review artifact for human stakeholders. It visualizes open questions, file maps, and planning comments that a standard markdown plan cannot render for architecture review.

You should not use automated architecture planning for refactoring tasks if your milestone lacks detailed software specifications or requires modifying the codebase during investigation. The process demands read-only codebase analysis and exact plan structure to preserve downstream audit requirements.