kiro-spec-tasks

Generate implementation tasks from requirements and design files.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-tasks-taku-o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-tasks
Source: https://github.com/taku-o/gitignore-merge/tree/main/.claude/skills/kiro-spec-tasks
Command: npx skills add https://github.com/taku-o/gitignore-merge --skill kiro-spec-tasks-taku-o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts ambiguous or high-level product requirements and design documents into a concrete, executable task plan so engineering teams can start implementation without ambiguous handoffs or hidden prerequisites. It enforces requirement coverage, task granularity, and explicit dependency and boundary annotations so work is verifiable and parallel-safe where appropriate.

Core Features & Use Cases

  • Automated Task Generation: Reads .kiro/specs/{feature}/requirements.md and design.md and produces a structured tasks.md that maps numeric requirement IDs to executable 1–3 hour sub-tasks.
  • Quality & Safety Gates: Runs rule-based reviews, a task-plan review gate, and an independent task-graph sanity check to catch hidden prerequisites, cross-boundary issues, and oversized tasks before writing tasks.md.
  • Merging & Approval Workflows: Merges with existing tasks.md when present, updates spec.json approval metadata, and supports auto-approve and interactive approval flows.
  • Use Case: Turn a completed spec for feature "checkout" into a merged, reviewed, and approval-ready .kiro/specs/checkout/tasks.md for immediate implementation.

Quick Start

Run the kiro-spec-tasks skill for feature checkout to generate and validate .kiro/specs/checkout/tasks.md.

Frequently Asked Questions about kiro-spec-tasks

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

FAQPage Schema
How do I convert requirements and design documents into implementation tasks?

To convert requirements and design documents into implementation tasks, you can generate a structured tasks.md that maps numeric requirement IDs from your specs into executable 1-3 hour sub-tasks with explicit dependencies and boundary annotations.

What is the best way to generate parallel-safe implementation tasks from a spec?

Generating parallel-safe implementation tasks from a spec requires applying parallel analysis markers and running an independent task-graph sanity check to catch hidden prerequisites and cross-boundary issues before finalizing your task plan.

How do I merge newly generated tasks with an existing tasks.md file?

To merge newly generated tasks with an existing tasks.md file, apply a merging workflow that combines new sub-tasks with your current task plan while updating the approval metadata in your spec.json file.

Can I automate task generation for my .kiro/specs workflows?

You can automate task generation for .kiro/specs workflows by reading requirements.md and design.md to produce a structured, approval-ready tasks.md file that enforces requirement coverage and task granularity for immediate implementation.

Why do I need a task-plan review gate when creating executable sub-tasks?

A task-plan review gate is needed when creating executable sub-tasks to run rule-based reviews that catch oversized tasks, hidden prerequisites, and cross-boundary issues before writing the final tasks.md file.

Does spec-to-tasks generation support auto-approve and interactive approval flows?

Spec-to-tasks generation supports both auto-approve and interactive approval flows by updating the spec.json approval metadata during the task generation and merging process.