task-decomposition

Task decomposition converts high-level OAK plans into a structured task hierarchy of Epics, Stories, and Subtasks. The generated tasks.md file organizes work into a standardized structure suitable for sprint planning and direct export to GitHub Issues.

The required file structure enforces a consistent oak/plan/<name>/ directory layout containing plan.md, optional research, and the generated tasks.md. This standardization streamlines collaboration and ensures plans are discovered via required frontmatter containing name and description.

Yes, task decomposition supports sprint planning by producing a coherent tasks.md file that structures implementation phases. This structured work output aligns directly for issue export to Azure DevOps, ensuring sprint-ready mapping from plan goals to actionable tasks.

Yes, you must create a plan under the oak/plan/<name>/ directory with a plan.md file and optional research folder. Running the plan-tasks command then processes these inputs to generate the tasks.md file and align your work for export.

Task decomposition maps high-level goals and research into a structured task hierarchy containing Epics, Stories, Tasks, and Subtasks. This approach translates abstract implementation plans into executable sets that guide both implementation tracking and issue export.