breakdown-tasks

Breaks specs and feature requests into small trackable task and epic files.

Updated May 13, 2026
One-click install
npx skills add https://github.com/andrewcodesit/skills --skill breakdown-tasks-andrewcodesit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-tasks
Source: https://github.com/andrewcodesit/skills/tree/main/skills/project-management/breakdown-tasks
Command: npx skills add https://github.com/andrewcodesit/skills --skill breakdown-tasks-andrewcodesit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a spec or project idea into actionable work items is often ad hoc: tasks end up too large, untracked, or locked into one vendor's tool. This Skill converts any spec, feature request, or implementation goal into small, session-sized tasks with clear acceptance criteria, stored locally or in a connected external system. ## Core Features & Use Cases - Spec-to-task decomposition: Splits a spec into tasks small enough for one focused agent session, each with a goal, acceptance criteria, and validation steps. - Optional epic grouping: Organizes larger specs into epics when the work naturally splits into milestones, modules, or phases. - Vendor-neutral tracking: Writes tasks to a global or repo-local Markdown board, or creates them in a connected external project-management system. - Use Case: You have a feature spec for a new settings page. Ask the agent to break it into tasks, and it produces a TASKS.md index plus individual TASK-001, TASK-002 files with testable acceptance criteria, ready to hand to an execution session. ## Quick Start Ask the agent to break this spec into tasks and track them on a local task board.

Frequently Asked Questions about breakdown-tasks

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

FAQPage Schema
How do I break a spec into tasks with an AI agent?▼

Provide the spec and ask the agent to break it into tasks. The Skill splits the work into items small enough for one focused session, each with a goal, acceptance criteria, and a validation command or manual check.

How do I create epics and tickets from a feature request?▼

Ask the agent to create tasks from the feature request and choose a storage location. Epics are created only when the spec naturally splits into multiple outcomes, modules, or phases, and never for fewer than four tasks unless clearly useful.

Can I use this with Jira or other project-management tools?▼

Yes, if a connected project-management MCP, plugin, or tool is available, tasks can be created there instead of locally. The Skill stays vendor-neutral and maps epics to parent tasks, labels, or milestones when native epics are unsupported.

Where are the generated task files stored?▼

Tasks are stored either in a global board at ~/.agents/tasks/<repo>/<project-slug>/ or a repo-local board at .agents/tasks/<project-slug>/. Each board has a TASKS.md index plus individual task files, optionally organized under an epics directory.

When should I not use task breakdown for a spec?▼

Do not use it to plan implementation details; that belongs to a separate planning skill. Task files capture goals and acceptance criteria only, and exclude commit, push, or pull request steps.