spec-to-tasks

Decomposes specified tickets into approved, self-contained implementation tasks with executor classifications and blocking edges.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/bbenefield89/skills --skill spec-to-tasks-bbenefield89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-to-tasks
Source: https://github.com/bbenefield89/skills/tree/main/skills/spec-to-tasks
Command: npx skills add https://github.com/bbenefield89/skills --skill spec-to-tasks-bbenefield89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a written ticket specification into executable work items is error-prone: tasks end up too coarse, lack context for a fresh worker, miss blocking relationships, or drift from the parent ticket. This Skill decomposes a specified ticket into tracer-bullet child tasks that are individually verifiable, correctly classified, and linked to their parent. ## Core Features & Use Cases - Tracer-bullet decomposition: Breaks a specification into narrow, end-to-end tasks that each fit a fresh context window and are demoable on their own. - Executor classification and blocking graph: Assigns each task exactly one agent or human executor, declares genuine blocking edges, and publishes them to the configured tracker with parent relationships. - Parent task sequence table: Prepends a generated task table to the parent ticket while preserving the rest of the body byte-for-byte. - Use Case: After a feature ticket's specification is approved, run this Skill to produce a reviewed, dependency-ordered set of child tasks published to your issue tracker, each with acceptance criteria and blocker links. ## Quick Start Ask the AI to break the specified ticket into implementation tasks using the spec-to-tasks skill and publish them to the configured tracker.

Frequently Asked Questions about spec-to-tasks

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

FAQPage Schema
How do I break a ticket specification into implementation tasks?

Provide the specified parent ticket and the Skill drafts tracer-bullet tasks that each cut a complete path through relevant layers. You review granularity, executors, and blockers before anything is published to the tracker.

What is a tracer-bullet task in ticket decomposition?

A tracer-bullet task is a narrow but complete vertical slice covering schema, API, UI, and tests where applicable. Each task is demoable on its own and sized to fit in a single fresh context window.

How are agent versus human executors assigned to tasks?

Tasks that can be completed autonomously with available tools and access receive the configured agent executor. Tasks requiring human-only judgment, access, physical action, or manual validation receive the configured human executor.

How does it handle wide refactors that cannot fit one task?

Wide refactors use an expand-contract pattern: add the new form beside the old, migrate callers in verifiable batches, then remove the old form. The expand task blocks every migration and the contract task is blocked by every migration.

Does it modify the parent ticket when publishing tasks?

It only prepends or refreshes a generated task sequence table at the top of the parent body. The rest of the parent content remains byte-for-byte unchanged, and neither the parent nor any task is closed.

What happens if task publication fails partway through?

Publication stops on partial failure and reports exactly what was created, changed, and left incomplete. Every task, classification, parent edge, and blocker edge is verified before the run is considered complete.