kiro-spec-tasks

To generate implementation tasks from product requirements, apply this skill to feature-level specs, converting numeric requirement IDs into sequenced, reviewable task plans with explicit dependencies and sizing.

Sequencing feature implementation tasks for parallel execution involves producing 1-3 hour sub-tasks and applying optional parallel (P) markers with boundary annotations to define independent execution paths.

Yes, you need approved requirements and design documents before creating an executable task plan, as the review gate halts generation when specs are unapproved or underspecified to ensure full coverage.

Yes, you can merge new implementation tasks into an existing tasks.md file located in the .kiro/specs/{feature} directory, which updates the spec.json metadata and preserves existing task structures.

To automate task generation without manual approval, invoke the skill with the feature name and an explicit auto-approve flag, bypassing the standard review gate for automated workflow execution.

Requirement mapping fails when design documents are underspecified because an independent sanity review halts the process, ensuring every requirement is mapped to a verifiable, correctly sized task before proceeding.