plan

To generate a structured project plan with acceptance criteria, you define the feature scope and execute a planning workflow that maps surface area, establishes testable criteria, and produces an executable multi-phase blueprint.

A cabinet critique in project planning is an optional review phase that surfaces concerns and identifies potential misaligned work before implementation begins. Use it to prevent dead code and validate decisions on complex infrastructure or design projects.

You create multi-phase plans for infrastructure and code projects by applying a reusable workflow that includes research, overlap-checks, plan templating, and completeness checks, ensuring cold-start readiness for future sessions.

Yes, you can use this planning workflow for both design and infrastructure projects. It applies structured surface-area mapping and testable acceptance criteria across code, design, and infrastructure planning to ensure alignment.

The best way to prevent dead code and misaligned work is to enforce precise surface-area mapping and apply an optional cabinet critique phase during planning, which surfaces dependencies and concerns before execution starts.

You need to document decisions and dependencies for cold-start readiness to ensure that future sessions can seamlessly resume multi-phase work without losing context on prior research, overlap-checks, and completed plan phases.