maestro:blueprint

To generate an implementation spec for a multi-file change, you explore the relevant codebase areas and synthesize a structured plan. This produces a markdown plan with phases, tasks, and acceptance criteria alongside a visual HTML architecture overview.

The best way to visualize feature architecture is generating a themed HTML blueprint with Mermaid diagrams. It maps the codebase and presents an interactive timeline, per-phase file breakdowns, and a risk matrix for quick human review.

Codebase exploration for architecture planning guides parallel checks across bounded contexts, infra, shared modules, and tests. It identifies critical files and existing tracks to ensure the generated plan spec accurately reflects the current project structure.

You need a project structure with bounded contexts like `src/features/`, `src/infra/`, and `src/shared/` to map effectively. The feature blueprint generation checks these directories to identify critical files and design dependencies for the plan.

A phase-based implementation plan includes context, critical files, design decisions, and sequential phases. Each phase contains specific tasks, acceptance criteria, verification steps, risks, and dependencies saved directly as a markdown spec.

Mermaid diagrams provide visual dependency graphs and architecture visualizations for complex feature changes. They help developers quickly understand multi-file interactions and track phase-based tasks within the generated HTML blueprint overview.