kiro-spec-tasks

Generate implementation task plans from approved specification requirements and design documents.

Updated Jun 23, 2026
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-tasks-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-tasks
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/kiro-spec-tasks
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill kiro-spec-tasks-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved requirements and design specification into an executable, well-structured implementation task list is slow and error-prone, often leaving requirements uncovered or tasks with hidden dependencies. ## Core Features & Use Cases - Requirements-to-Tasks Mapping: Reads spec.json, requirements.md, and design.md to generate a tasks.md where every requirement ID is covered by at least one task. - Parallel Execution Analysis: Marks tasks with (P) when they have non-overlapping component boundaries and no data dependencies, enabling concurrent implementation. - Built-in Review Gates: Runs a task plan review and an independent task-graph sanity check before writing tasks.md, catching coverage gaps, sizing issues, and dependency mistakes. - Use Case: After approving requirements and design for a new feature, run the skill to produce a localized tasks.md with 1-3 hour sub-tasks annotated with Requirements:, Boundary:, and Depends: fields, then hand off to implementation. ## Quick Start Ask the AI to generate implementation tasks for your approved spec by running the kiro-spec-tasks skill with your feature name, optionally adding -y to auto-approve requirements and design.

Frequently Asked Questions about kiro-spec-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate implementation tasks from a specification?

Run the skill with your feature name after requirements.md and design.md exist and are approved. It reads the spec files, applies task generation rules, and writes a tasks.md with numbered tasks mapped to requirement IDs.

How do I mark tasks for parallel execution in a task plan?

Tasks are marked with (P) when they have no data dependencies, no shared file conflicts, and non-overlapping _Boundary:_ component scopes. Use the --sequential flag to omit all (P) markers and force sequential execution.

Can I auto-approve requirements and design when generating tasks?

Yes, pass the -y flag to auto-approve requirements and design in spec.json and proceed directly to task generation. Without it, the skill stops if either phase is not already approved.

Why does task generation stop with a missing requirement ID error?

All requirements in requirements.md must have numeric IDs so tasks can map coverage via _Requirements:_ annotations. If any requirement lacks an ID, generation stops and you must fix requirements.md first.

What happens if the task review finds a gap in the design?

The skill stops without writing tasks.md and returns a RETURN_TO_DESIGN verdict pointing to the exact gap. You must refine requirements.md or design.md and re-run generation rather than patching over the gap.