skills.rest
tdp1999
tdp1999COMMUNITY
Explore all skills by this author →
WebsiteGitHub

breakdown

Convert epics, investigations, or features into actionable task files with acceptance criteria and dependencies in .context/tasks/.

Updated Feb 11, 2026
Search Tags:#planning#investigation#epic#breakdown#task#task-generation#context-bank
One-click install
npx skills add https://github.com/tdp1999/claude-code-ctx --skill breakdown-tdp1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown
Source: https://github.com/tdp1999/claude-code-ctx/tree/main/plugins/ctx/skills/breakdown
Command: npx skills add https://github.com/tdp1999/claude-code-ctx --skill breakdown-tdp1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down a feature, plan, epic, or investigation into actionable task files within the .context/tasks/ folder, enabling clear scope, traceability, and incremental progress.

Core Features & Use Cases

  • Create a structured set of tasks with explicit acceptance criteria, dependencies, and progress tracking.
  • Update epic or investigation statuses and reflect progress in the central context bank.
  • Provide reusable templates and references to ensure consistent task quality and handoffs.

Quick Start

Create a breakdown by selecting an epic or investigation to break down, or provide an ad-hoc feature description, then let the assistant generate tasks and update statuses.

Frequently Asked Questions about breakdown

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

FAQPage Schema
How do I break down an epic into actionable tasks?▼

To break down an epic, you select the epic or provide an ad-hoc feature description, and the tool generates a structured set of actionable task files with clear acceptance criteria, dependencies, and progress linkage.

What is task generation for software investigations?▼

Task generation for investigations converts high-level plans or ideas into structured task files within a project context bank, ensuring traceability and incremental progress tracking.

How do I track progress and dependencies for generated tasks?▼

You track generated tasks by utilizing explicit acceptance criteria, dependency records, and status updates that link back to the source epic or investigation within the context bank.

Can I use this for ad-hoc feature requests without a predefined epic?▼

Yes, you can process ad-hoc feature requests by providing a feature description, which the tool then converts into structured task files with progress tracking and context bank updates.

What's the best way to ensure task traceability during epic breakdown?▼

The best way to ensure task traceability is generating tasks with explicit references and dependencies, updating the source epic status, and recording progress in the central context bank.

Related Skills

Explore More Software Engineering Skills→
zhixuan312zhixuan312
5

mma-delegate

Dispatch ad-hoc tasks to workers and return structured per-task reports.

Community
Advanced
u9401066u9401066

memory-updater

Update Memory Bank files with progress, decisions, and focus notes.

Community
Basic
roderikroderik
2

subagent-driven-development

Dispatch fresh subagents per task to execute implementation plans with two-stage reviews.

Community
Advanced
kimon1230kimon1230
4

compress

Manually compress Claude session progress entries with a custom Python compressor module.

Community
Intermediate