kiro-spec-tasks

Generating executable task plans involves automating the translation of requirements.md and design.md into hierarchical tasks. This process produces a complete task graph with sub-tasks, boundaries, and dependencies.

Task planning automation rules enforce sub-tasks sized at 1-3 hours with clear boundaries and optional parallel markers. This ensures observable completion criteria and proper dependency mapping for all numeric IDs.

Merging new tasks into an existing tasks.md file preserves design integrity and requirements coverage. The automation reads the current file alongside requirements and design documents to seamlessly update the task hierarchy.

Kiro-spec-tasks works with existing requirements and design specs by reading requirements.md and design.md from the .kiro/specs directory. It uses these inputs to produce a complete and executable task graph.

Enforcing observable completion criteria is best achieved through automated task generation that maps requirements directly to tasks. This ensures all numeric IDs have clear mappings and generation rules are strictly satisfied.

Automated task generation should not be used when your feature lacks finalized requirements.md or design.md documents. The automation requires these specific input files to produce a valid hierarchical tasks.md output.