skills.rest
IKatsuba
IKatsubaCOMMUNITY
Explore all skills by this author →
Website𝕏@katsuba_igorGitHub

spec:tasks

Generate implementation tasks documents from .specs requirements and design files.

1|Updated Jan 21, 2026
Search Tags:#design#planning#documentation#requirements#specifications#tasks#generate
One-click install
npx skills add https://github.com/IKatsuba/skills --skill spec-tasks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec:tasks
Source: https://github.com/IKatsuba/skills/tree/main/spec/tasks
Command: npx skills add https://github.com/IKatsuba/skills --skill spec-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of an implementation plan by converting requirements and design documents into a structured tasks document.

Core Features & Use Cases

  • Automatic task generation: Reads .specs/<spec-name>/requirements.md and design.md to produce a detailed tasks list with subtasks and checkpoints.
  • Cross-check & verification: Validates the plan against the codebase to surface discrepancies and dependencies.
  • Real-world use case: Given a spec named payments, generate a tasks document that breaks down features into actionable steps with tests and checkpoints.

Quick Start

Provide a spec name to generate its tasks document, or let the skill list available specs in .specs/ when none is given.

Frequently Asked Questions about spec:tasks

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

FAQPage Schema
How do I generate implementation tasks from software requirements and design documents?▼

To generate implementation tasks, provide a spec name so the tool can read your requirements.md and design.md files to produce a structured tasks list with subtasks and checkpoints.

Can I automatically break down project specifications into testable subtasks?▼

Yes, you can break down specifications into testable subtasks by running the skill on a named spec, which analyzes design artifacts and cross-checks the codebase to validate dependencies.

What is the best way to plan development tasks from a .specs documentation folder?▼

The best way to plan development tasks is to use a specification parser that reads .specs documents to locate relevant files and output a structured tasks.md file with progress checkpoints.

Does generating a tasks document require both requirements and design artifacts?▼

Generating a tasks document requires both requirements.md and design.md artifacts within the .specs/<spec-name>/ directory to properly analyze design decisions and satisfy functional requirements.

What happens if I run the task generation without specifying a spec name?▼

If you run the task generation without specifying a spec name, the skill will list all available specifications found within the .specs/ directory for you to choose from.

How does the tool handle codebase discrepancies during task planning?▼

During task planning, the tool cross-checks the generated implementation plan against your actual codebase to surface discrepancies, identify dependencies, and add verification checkpoints.

Related Skills

Explore More Software Engineering Skills→
notta50notta50

kiro-validate-design

Review technical design documents and issue GO/NO-GO decisions.

Community
Advanced
QunnnnQunnnn

executing-plans

Execute written implementation plans through structured review and verification checkpoints.

Community
Intermediate
Steve-Smith-CODESteve-Smith-CODE

speckit-tasks

Generate dependency-aware task lists from spec.md and plan.md files.

Community
Intermediate
qodex-aiqodex-ai
39

specification-executor

Transforms workspace specification documents into structured implementation plans and tasks.

Official
Advanced