kiro-spec-tasks

To generate a task plan from requirements and design documents, you map each requirement to discrete 1-3 hour sub-tasks with clear observable completion criteria. This task generation process enforces logical progression, explicit boundaries, and parity with design.md.

Breaking down project requirements into executable sub-tasks involves sizing each task to 1-3 hours and defining explicit boundaries when tasks cross system components. This approach ensures incremental progression and includes a lightweight sanity review to verify executability.

Generating a task plan from specs requires your project to store requirements and design documents in the .kiro/specs/{feature}/ directory. The generated task plan is then written directly to .kiro/specs/{feature}/tasks.md with metadata updated in spec.json.

Task generation rules ensure executability by enforcing observable deliverables and maintaining parity with design.md. They require sequential or parallel execution marks and explicit dependencies, verifying the task graph sanity before finalizing tasks.md.

You can update spec.json metadata automatically when creating task plans. The task generation process writes the complete executable task plan to tasks.md and concurrently performs a metadata update in spec.json.

Task boundaries should be explicitly defined when crossing system components to ensure logical and incremental task progression. This prevents scope ambiguity and maintains clear observable completion criteria for each 1-3 hour executable task.