spec-kitty.tasks

Name: spec-kitty.tasks
Availability: InStock
Author: kimprobably

Generate work-package breakdowns and tasks.md files from mission spec and plan artifacts.

Updated May 13, 2026

Search Tags:#dependency mapping #spec decomposition #agent planning #mission planning #work packages #code execution lanes #project branching

Ready to run

npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-tasks-kimprobably

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-kitty.tasks
Source: https://github.com/kimprobably/maestro-os/tree/main/.agents/skills/spec-kitty.tasks
Command: npx skills add https://github.com/kimprobably/maestro-os --skill spec-kitty-tasks-kimprobably

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts an abstract feature plan into concrete, reviewable work packages so multiple agents can implement the feature correctly and in parallel.

Core Features & Use Cases

Plans to work packages: Breaks a plan into well-sized work packages with clear objectives, implementation sketches, risks, and dependencies.
Deterministic planning workflow: Enforces correct planning branch context resolution and safe workspace handling in the project root checkout.
Execution-ready artifacts: Generates tasks.md and one prompt file per work package so implementers can proceed without digging into design docs.

Quick Start

Run the spec-kitty tasks skill for your mission to generate feature_dir/tasks.md and the work-package prompt files in feature_dir/tasks.

Frequently Asked Questions about spec-kitty.tasks

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

FAQPage Schema

How do I decompose a project plan into work packages for parallel agent execution?▼

Spec decomposition breaks an abstract feature plan into concrete work packages with clear objectives, implementation sketches, risks, and dependencies so multiple agents can implement the feature in parallel.

What is the best way to generate execution-ready task files from a mission plan?▼

Generating execution-ready artifacts creates a tasks.md file and one prompt file per work package in the feature directory, allowing implementers to proceed without digging into design docs.

How does dependency mapping work when creating work packages for code execution lanes?▼

Dependency mapping validates work package sizing and ownership, finalizing each package with dependency-aware metadata to ensure safe ownership boundaries across parallel code execution lanes.

Do I need a specific project branching strategy to generate work package prompts?▼

Yes, deterministic planning enforces correct planning branch context resolution and safe workspace handling in the project root checkout before generating work package prompt files.

Can I use mission planning artifacts to support parallel implementation by agents?▼

Mission planning converts a roadmap's spec and plan artifacts into a detailed work-package breakdown, validated for sizing and ownership, to directly support parallel implementation by agents.

What are the limitations of breaking down a feature plan into work packages?▼

Work package generation requires resolver-provided context paths and branches, and must run finalize-tasks with validation to ensure safe ownership boundaries, limiting ad-hoc task creation outside this workflow.