skills.rest
camercu
camercuCOMMUNITY
Explore all skills by this author →
GitHub

to-tasks

Breaks plans and specs into independently implementable vertical-slice tasks.

2|2|Updated Jun 28, 2015
Search Tags:#planning#task breakdown#agile#github issues#spec#vertical slice#tracer bullet
One-click install
npx skills add https://github.com/camercu/dotfiles --skill to-tasks-camercu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tasks
Source: https://github.com/camercu/dotfiles/tree/main/common/.config/agents/skills/to-tasks
Command: npx skills add https://github.com/camercu/dotfiles --skill to-tasks-camercu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a spec or plan into actionable work often produces tasks that are too large, horizontally layered, or blocked by hidden dependencies. This Skill converts specs, GitHub issues, or loose descriptions into thin, end-to-end vertical slices that are each demoable and implementable in a single session. ## Core Features & Use Cases - Vertical Slice Decomposition: Every task is a tracer bullet cutting through all layers (schema, API, logic, UI, tests), starting with a walking skeleton as Task 1. - Structured Task Metadata: Each task includes a title, HITL/AFK classification, spec requirement coverage, and dependency ordering. - Iterative Refinement: Presents a lightweight numbered draft for user feedback on granularity, dependencies, and classifications before fleshing out acceptance criteria. - Use Case: After drafting a feature spec with /to-spec, run this Skill to produce a flat markdown task list where Task 1 proves the architecture end-to-end and later tasks flesh out the working core. ## Quick Start Ask the AI to break the current spec or GitHub issue into vertical-slice implementation tasks using to-tasks.

Frequently Asked Questions about to-tasks

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

FAQPage Schema
How do I break a software spec into implementation tasks?▼

Use vertical slicing: define each task as a thin end-to-end path through all layers (schema, API, logic, UI, tests) rather than one layer at a time. Start with a walking skeleton task that proves the architecture works, then flesh out from that core.

What is a vertical slice in task breakdown?▼

A vertical slice is a narrow but complete path through every integration layer of a system, delivering demoable behavior on its own. It contrasts with horizontal slices like "set up the database" which produce no user-visible value alone.

How do I know if a task is too big to implement?▼

A task is too thick if it takes more than one session to implement or cannot be demoed independently. Split it into thinner slices, preferring many small end-to-end tasks over a few large ones.

Can I generate tasks from a GitHub issue?▼

Yes, the Skill accepts GitHub issues as input, fetched with comments via gh issue view. It also works from /to-spec output, conversation context, or loose feature descriptions.

When should I not use vertical slicing for tasks?▼

Avoid forcing vertical slices when a known weakness exists, such as fragile code or missing tests. Schedule a repair slice first, since building on an unstable foundation makes later slices harder to verify.

Related Skills

Explore More Software Engineering Skills→
ayazhankadessovaayazhankadessova

open-issue

Drafts GitHub issues from conversation context using the GitHub CLI for creation.

Community
Intermediate
authrain-cloud-abdullahformuliauthrain-cloud-abdullahformuli

incremental-implementation

Implements code changes in thin, tested vertical slices with per-increment commits.

Community
Intermediate
MichaelSolatiMichaelSolati

tdd

Guide red-green-refactor cycles with behavior-focused integration tests.

Community
Intermediate
oakossoakoss
14

tracer-bullets

Implement features as verified vertical end-to-end slices across application layers.

Official
Intermediate