sprint-planner

Decomposes approved specs into atomic GitHub issues within a new sprint milestone.

Updated Jul 13, 2024
One-click install
npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill sprint-planner-reading-advantage-thailand
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-planner
Source: https://github.com/Reading-Advantage-Thailand/codecamp-advantage/tree/main/.claude/skills/sprint-planner
Command: npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill sprint-planner-reading-advantage-thailand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, yq, jq, and includes scripts (resource) components.

What problem does it solve? Converting an approved specification into actionable development work is tedious: someone must read the spec, break it into atomic tasks, and manually create labeled GitHub issues under a milestone. This Skill automates that sprint planning workflow end to end. ## Core Features & Use Cases - Automated Issue Creation: Parses a tasks.yml file and creates a GitHub issue per task, each linked to a parent Epic and assigned to a sprint milestone. - Milestone & Label Management: Creates the sprint milestone if missing and auto-provisions type, component, and priority labels with color coding. - Validation & Traceability: Validates YAML structure and required fields before execution, and every issue references its parent Epic for traceability. - Use Case: A tech lead finishes a spec review, runs the script against docs/changes/sprint-7/tasks.yml, and gets a fully populated GitHub milestone with labeled task issues ready for team review. ## Quick Start Ask the assistant to plan a new sprint from the approved spec by running the sprint planning script and creating GitHub issues under a new milestone.

Frequently Asked Questions about sprint-planner

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

FAQPage Schema
How do I create GitHub issues from a spec file automatically?▼

Define your tasks in a tasks.yml file with an epic field and a tasks array containing title, description, and labels. Run the create-sprint-issues.sh script, which validates the YAML, creates a milestone and parent Epic, then generates one labeled GitHub issue per task.

How to plan a sprint using the GitHub CLI?▼

Use the gh CLI with a script that creates a milestone via the GitHub API, opens a parent Epic issue, and runs gh issue create for each task with milestone and labels. The script also auto-creates missing labels with color coding.

What tools are required to run the sprint planning script?▼

The script requires the gh CLI authenticated to your repository, yq for parsing the tasks.yml file, and jq for JSON processing of GitHub API responses. All three must be installed and available in your system PATH.

Why does the sprint script fail with missing field errors?▼

The script validates that tasks.yml contains a root-level epic field and a non-empty tasks array, and that each task has title, description, labels.type, and labels.component. Tasks missing required fields are skipped with an error message.

Can I reuse an existing GitHub milestone for sprint planning?▼

Yes. The script checks whether the milestone name you enter already exists via the GitHub API. If found, it reuses that milestone instead of creating a duplicate, then assigns all new issues to it.