kiro-spec-tasks

Breaking down a specification into actionable work items requires mapping requirements to tasks with clear deliverables. This skill translates your spec into a concrete plan where every sub-task has observable completion criteria and a verifiable deliverable.

Sequencing implementation tasks with clear dependencies involves mapping requirements to a structured plan. This skill analyzes your spec to produce a sequenced task plan where each item is sized for 1-3 hours with explicit boundaries and dependencies defined.

Marking tasks for parallel analysis support involves identifying safe execution paths. This skill marks tasks as (P) when safe and defines clear boundaries to enable parallel work, ensuring your project management workflow supports concurrent execution.

Task generation works directly with specs stored in the .kiro/specs directory. Running the generator against your current spec produces a full implementation task plan with explicit dependencies and observable deliverables.

Automated task generation from specifications depends on the completeness of your spec and supporting rules. If design boundaries are unclear or requirements lack detail, the generated task plan may require additional manual review before execution.

Each generated task needs observable completion criteria to ensure verifiable deliverables such as a file, endpoint, or test result. This validation mechanism guarantees that every requirement mapped from your spec is properly executed and validated.