plan-derivetasks

To convert requirements and goals into an actionable task breakdown, process your analyzed project artifacts like requirements.json and goals.json to generate structured work items, acceptance criteria, and phase definitions. This creates traceable tasks ready for execution.

Generating task dependencies and acceptance criteria from project goals involves mapping analyzed requirements to identify execution order and success conditions. This process produces a structured task plan with clearly defined deliverables and resolved dependency chains.

Yes, you can output a task breakdown as both JSON and Markdown from analyzed requirements. The conversion produces a programmatic task-breakdown.json file for automation and a human-readable task-breakdown.md report for team consumption.

Creating structured task phases from a w5h-analysis file requires placing the artifact under your project's analysis directory. Processing this input generates phase definitions, per-task files, and standardized templates with categories and estimates.

Yes, you need specific input artifacts like requirements.json, goals.json, or w5h-analysis.json placed under your project's analysis directory. These analyzed inputs provide the foundational requirements and objectives needed to produce the task breakdown.

Automated task breakdown generation should not be used when you lack analyzed requirement artifacts like requirements.json or goals.json. The mechanism depends entirely on these structured inputs to map dependencies and produce executable phase definitions.