deep-plan

Planning complex features involves creating an entry-point architecture document and decomposing the workstream into executable sub-plans. This structures big initiatives by generating a dependency graph and time budgets to optimize parallelism across multiple files and systems.

Sub-plan decomposition is the process of breaking a large architecture document into executable sub-plans, such as G1 or G2 files. It structures big workstreams by creating a plan folder layout with dependency graphs to optimize parallelizable tasks across multiple sprints.

Integrate security reviews and risk assessment into architecture planning by enforcing them directly within the plan generation process. This includes conducting one-way door analysis and establishing guardrails to reduce risk and ensure timely delivery of complex features.

You need a dependency graph for parallelizable workstreams when planning complex initiatives spanning multiple files and systems. Generating a dependency graph with time budgets optimizes parallelism by structuring executable sub-plans within a dedicated plan folder layout.

The best way to structure an entry-point architecture document is to use an 00-*.md file format within a docs/plans folder structure. This entry point defines the architecture analysis and links to associated executable sub-plans to structure big workstreams effectively.

This planning approach is not intended for single-file updates or simple feature additions. It applies to initiatives spanning multiple files and systems, requiring architectural decisions, multi-sprint planning, and parallelizable workstreams to justify the sub-plan decomposition overhead.