kiro-spec-tasks

Generates milestone-based implementation task lists from approved requirements and design documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scapia-oss/compass --skill kiro-spec-tasks-scapia-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-tasks
Source: https://github.com/scapia-oss/compass/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-spec-tasks
Command: npx skills add https://github.com/scapia-oss/compass --skill kiro-spec-tasks-scapia-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning approved requirements and design documents into an executable implementation plan is error-prone: tasks end up too large, miss requirements, hide dependencies, or lack verifiable outcomes. This Skill converts spec artifacts into a structured tasks.md file where every requirement maps to a milestone with test steps, boundaries, and verification gates. ## Core Features & Use Cases - Milestone Task Generation: Produces major tasks as verify-and-commit units with test steps, scoped integration gates, and evidence bullets, sized at 1-3 hour steps. - Coverage and Sanity Review: Runs a task plan review gate plus an independent task-graph sanity review to catch missing requirements, hidden prerequisites, and dependency errors before writing tasks.md. - Lifecycle and Approval Handling: Validates requirement/design approvals, supports auto-approve mode, updates spec.json phase metadata, and hands off to implementation commands. - Use Case: After approving requirements and design for a new notifications feature, run the Skill to produce a tasks.md with parallelization markers, boundary annotations, and requirement traceability, ready for autonomous implementation. ## Quick Start Ask the AI to generate implementation tasks for your feature by running the kiro-spec-tasks command with your feature name after requirements and design are approved.

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 spec?

Run the kiro-spec-tasks command with your feature name after requirements and design are approved. It reads spec.json, requirements.md, and design files, then writes a milestone-structured tasks.md mapping every requirement to executable tasks.

How do I auto-approve requirements and design for task generation?

Pass the -y flag with the feature name to auto-approve requirements, design, and tasks in one run. This skips interactive review, so it is recommended only for low-risk specs.

Can I generate tasks without a design document?

Yes, for simple bugfixes or specs where design artifacts are disabled, tasks are generated from requirements or bugfix analysis alone. The Skill loads only the artifacts enabled in spec.json.

What happens if requirements are not approved before task generation?

Execution stops with a message that requirements and design must be approved first. You can either approve them manually and re-run, or use the -y flag to auto-approve all phases.

Why does task generation stop with a RETURN_TO_DESIGN verdict?

The task-graph sanity review found gaps or contradictions in requirements or design that prevent an executable plan. Refine the requirements or design documents, then re-run task generation.