flow-plan

To turn a feature request into an actionable build plan, provide the text request or bead ID to generate a structured markdown plan with tasks, dependencies, and acceptance criteria. The workflow covers discovery, gap analysis, depth selection, and plan generation.

Yes, you can generate work breakdowns from plain text bug reports by processing them through the discovery and gap analysis workflow. This converts unstructured text into structured task files ready for review or execution.

The best way to convert a bead ID into structured tasks is to input the identifier directly. The workflow automatically applies discovery and depth selection to output executable plans, markdown files, or new beads.

Yes, this workflow planning method supports architecture planning alongside feature and work breakdown planning. It applies discovery, gap analysis, and depth selection to convert architectural requests into structured, executable plans.

To ensure generated plans align with existing team conventions, the workflow reuses existing standards and planning templates during generation. This maintains consistency across teams while producing structured markdown plans or task files.