Sprint Planner FAQs

Question 1

What tools are required to run the Sprint Planner?

Accepted Answer

To use this skill effectively, you need the GitHub (gh) CLI, the Gemini CLI, and jq installed and authenticated on your system. Your project should also have a GitHub project board configured with an 'Approved Backlog' status.

Question 2

Can I review the tasks before they are finalized?

Accepted Answer

Yes. The workflow is designed for collaboration. After the AI generates the task list and creates the issues, the skill includes a dedicated step for you to walk through the issues with your team to confirm completeness, adjust priorities, and make manual refinements.

Question 3

When should I use this Claude Code skill?

Accepted Answer

Use this skill at the beginning of a new sprint or development cycle. It is ideal for situations where you have an approved technical specification or Epic and need to quickly generate a comprehensive, structured backlog of implementation tasks.

Question 4

How does AI-driven decomposition improve my workflow?

Accepted Answer

Traditional scripts rely on rigid formatting; however, this skill uses Gemini AI to understand the actual content of your documentation. This results in more logical task breakdowns, reduces manual entry errors, and ensures that every part of a specification is accounted for in your GitHub project board.

Question 5

What does the Sprint Planner skill do?

Accepted Answer

The Sprint Planner skill automates the transition from high-level project specifications to actionable developer tasks. It uses the Gemini CLI to analyze your spec files and intelligently decomposes them into atomic GitHub issues, complete with milestone assignments and traceability links.

Sprint Planner

Sprint Planner

主な機能

ユースケース

主な機能

ユースケース