kiro-spec-tasks

Generate executable task plans from requirements and design files.

1.5k|242|Updated Feb 16, 2017
One-click install
npx skills add https://github.com/growilabs/growi --skill kiro-spec-tasks-growilabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-spec-tasks
Source: https://github.com/growilabs/growi/tree/main/.claude/skills/kiro-spec-tasks
Command: npx skills add https://github.com/growilabs/growi --skill kiro-spec-tasks-growilabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate high-level requirements and design into concrete, executable tasks with clear deliverables, dependencies, and boundaries to accelerate implementation.

Core Features & Use Cases

  • Generate task plans by mapping requirements to tasks and aligning with design components or interfaces.
  • Support parallel and sequential task analysis, with explicit Depends: and Boundary: annotations.
  • Merge new task plans with existing tasks.md when present and ensure observable, testable deliverables.

Quick Start

Run the kiro-spec-tasks command with a feature name to generate a draft task plan.

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 executable tasks from product requirements and design docs?

You can generate executable tasks by mapping requirements.md and design.md files within the .kiro/specs directory to concrete tasks. The tool reads these files alongside spec.json to produce a tasks.md plan with dependencies and boundaries.

What is the best way to turn software design specifications into a sequential task plan?

The best way to turn design specifications into a task plan is by applying rule-based analysis to your design.md and requirements.md files. This process supports both sequential and parallel analysis modes to accurately structure task execution order and define component boundaries.

Can I merge new generated tasks with an existing tasks.md file?

Yes, you can merge newly generated task plans with an existing tasks.md file. The generation process detects the existing file and integrates the new tasks while maintaining observable, testable deliverables and existing dependency structures.

How do task dependencies and boundaries work when mapping requirements to tasks?

Task dependencies and boundaries are explicitly marked using _Depends: and _Boundary: annotations within the generated tasks.md file. This ensures tasks are executed in the correct order and remain within defined component interfaces during implementation.

Do I need spec.json to generate a task plan from requirements and design docs?

Yes, generating a task plan requires spec.json alongside requirements.md and design.md in the .kiro/specs directory. These files provide the necessary feature context and rules to accurately map product requirements into executable tasks.