kiro-spec-tasks

To generate executable tasks from requirements, this Skill maps numeric requirement IDs to 1-3 hour sub-tasks, ensuring full coverage and dependency declarations before outputting a validated tasks.md file.

Spec-driven task planning converts approved feature specs into actionable items. It marks safe concurrent work with parallel indicators or omits them for sequential execution based on your requested mode.

To merge new implementation tasks with an existing tasks.md, the workflow automatically detects the current file, merges the new validated task plan, and updates the spec.json with phase changes and approvals.

Yes, you can enforce dependency annotations and boundary checks during task generation. The workflow runs a Task Plan Review Gate and an independent sanity review to prevent hidden prerequisites and oversized items.

Yes, the task generation workflow directly supports feature specs stored under the .kiro/specs/{feature} directory, reading the requirements and design documents to produce a deterministic implementation plan.

Numeric requirement IDs are needed for generating a task plan because they enforce strict requirement-to-task mapping, ensuring every documented requirement is covered by 1-3 hour executable sub-tasks without gaps.