dev-blueprint

To plan large-scale refactoring across multiple sessions, you need a structured construction plan that maps dependencies and breaks work into PR-sized execution units. This ensures context is preserved and work can be picked up without prior knowledge.

Breaking down complex feature implementation into PR-sized tasks requires generating a multi-step construction plan. This approach automatically detects dependencies to identify parallel workstreams and maps them into self-contained execution units.

Cold-start execution for multi-step development plans works by providing a self-contained context brief for every step. This allows any agent to pick up the work without prior knowledge of the project or previous sessions.

Yes, you need git integration and access to project documentation to generate construction plans for legacy migrations. These are required to perform pre-flight checks and adversarial plan review against an anti-pattern catalog.

Yes, you can parallelize workstreams when automating workflow planning for software architecture. The planning process automatically detects and maps dependencies to identify which execution units can be worked on in parallel.

You should not use a multi-session build plan for simple, single-session development tasks. This approach is designed for complex, large-scale refactoring, feature implementation, and migration projects requiring clear dependency mapping.