decompose-to-tasks

Decomposes user stories into ordered implementation tasks with codebase references.

5|Updated Sep 9, 2017
One-click install
npx skills add https://github.com/hpcsc/dotfiles --skill decompose-to-tasks-hpcsc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decompose-to-tasks
Source: https://github.com/hpcsc/dotfiles/tree/main/link/common/claude/.claude/skills/decompose-to-tasks
Command: npx skills add https://github.com/hpcsc/dotfiles --skill decompose-to-tasks-hpcsc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a user story into an actionable implementation plan requires exploring the codebase, identifying affected files, and sequencing work correctly. This Skill automates that breakdown so developers get an ordered, codebase-aware task list instead of planning manually. ## Core Features & Use Cases - Story Decomposition: Breaks a user story (file, inline text, or pasted block) into baby-step implementation tasks ordered by dependency. - Codebase Exploration: Delegates to an agent that identifies affected files, existing patterns, and domain types before planning. - Interactive Refinement: Asks targeted clarifying questions on scope, ordering, and testing strategy, then iterates on the saved task list based on feedback. - Use Case: Given a story file describing a new API endpoint, produce a tasks/[story-name].md file with ordered tasks referencing the relevant controllers, models, and tests, ready to hand off to an /implement or /tdd workflow. ## Quick Start Ask the assistant to decompose your user story into implementation tasks by providing the story file path or pasting the story text.

Frequently Asked Questions about decompose-to-tasks

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

FAQPage Schema
How do I break down a user story into implementation tasks?▼

Provide the user story as a file path, inline text, or pasted block. The skill delegates decomposition to an agent that explores the codebase, identifies affected files and patterns, and saves an ordered task list to tasks/[story-name].md.

What input formats does task decomposition accept?▼

The skill accepts a file path to a story document, inline text, or a pasted block via the argument hint. If the story is ambiguous, it asks 1-2 clarifying questions about scope, dependencies, and ordering preferences before decomposing.

Does the decomposed task list include codebase references?▼

Yes. The delegated agent explores the codebase to identify affected files, existing patterns, and domain types, then includes these references in each task so implementers know exactly where to work.

Can I adjust the task list after it is generated?▼

Yes. After presenting the summary, the skill asks whether tasks need splitting, merging, reordering, or additions. Feedback is delegated back to the agent, which updates the saved file in place.

When should I not use automated story decomposition?▼

Avoid it when the story lacks clear acceptance criteria and you cannot answer scoping questions, or when the work is a trivial single-step change. The skill explicitly does not implement code, only plans tasks.