implementation-planning

Breaking down software features involves generating an implementation plan that sequences scaffolding tasks before feature work, documenting dependencies and acceptance criteria while referencing existing PRD, FRD, and ADR inputs.

Visualizing software architecture and dependencies is best achieved by generating Mermaid L0-L3 diagrams within your implementation plan, which map out system structure and task sequencing across backend, frontend, and infrastructure layers.

You can create an implementation plan from a PRD by enforcing a planning-only behavior that maps inputs to scaffolding tasks and acceptance criteria, outputting Mermaid diagrams and technical task lists without implementing code.

Yes, this planning approach supports documenting acceptance criteria by breaking down features into technical tasks across backend, frontend, and infrastructure, mapping each task to clear dependencies and PRD, FRD, or ADR inputs.

You need L0-L3 Mermaid diagrams for software implementation planning when a project requires visualizing complex architecture and task dependencies, enabling predictable delivery through clear sequencing of scaffolding and feature work.