Task Breakdown FAQs

Question 1

What does the Task Breakdown skill do?

Accepted Answer

This skill decomposes high-level user stories into granular, technical work items. It analyzes requirements to create specific tasks for frontend, backend, database, and DevOps layers, complete with testable acceptance criteria.

Question 2

What kind of acceptance criteria does it generate?

Accepted Answer

The skill produces standardized, testable acceptance criteria for every task. This includes specific success conditions like API response structures, UI rendering requirements, and database migration validations to ensure work is 'done-done'.

Question 3

How does this skill improve my development workflow?

Accepted Answer

It eliminates manual planning overhead by automatically identifying technical dependencies and sequencing tasks. By providing standardized templates and CRUD patterns, it ensures consistency across your project's issue tracking.

Question 4

Does it integrate directly with project management tools?

Accepted Answer

Yes, it features seamless integration with GitHub Projects. Using the `/re:create-tasks` command, Claude can automatically generate and track GitHub issues, linking them as child tasks to your primary user stories.

Question 5

When should I use this Claude Code skill?

Accepted Answer

Use this skill during sprint planning or whenever you need to translate a feature request into a concrete implementation plan. It is ideal for moving from the 'what' (user story) to the 'how' (technical execution).

Task Breakdown

Task Breakdown

主な機能

ユースケース

主な機能

ユースケース