planning-workflow

Planning workflows convert vague software ideas into actionable roadmaps by guiding early-stage initiatives through goal definition, task scoping, and architecture decisions before code is written. This ensures development teams receive ready-to-implement strategic plans.

The best way to structure architecture plans for handoffs is using self-contained markdown documents with YAML frontmatter. This format embeds execution instructions and references to ensure development teams fully understand the strategic roadmap and task dependencies.

To track dependencies when scoping software tasks, apply a bead-based task structuring methodology during project initiation. This approach enables deterministic execution and clear dependency tracking within your markdown-based planning documents.

Yes, you can use iterative refinement prompts during architecture reviews to achieve multi-model convergence on robust plans. These prompts accelerate the planning and review process by systematically refining the initial project strategy.

No specific external dependencies are required to initiate a project using this markdown planning methodology. It operates as a self-contained system relying on YAML frontmatter and embedded resource directories to produce ready-to-implement strategic plans.