pm-sprint-plan

Generate two-week sprint plans from GitHub issue backlogs with dependency detection.

3|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/auerbachb/claude-code-config --skill pm-sprint-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-sprint-plan
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/pm-sprint-plan
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill pm-sprint-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn an unstructured GitHub issue backlog into an actionable two-week sprint by detecting dependencies, scoring work against goals and OKRs, grouping independent tracks, and recommending team assignments so planning is fast and defensible.

Core Features & Use Cases

  • Dependency detection: Finds explicit blockers and implicit file/area conflicts, builds directed dependency graphs, and flags cycles for manual resolution.
  • Prioritization & OKR alignment: Scores issues by goal impact and OKR relevance, boosts root blockers with high leverage, and summarizes deferred low-priority work.
  • Parallel tracks & assignments: Groups work into independent parallel tracks, orders tasks within each track, and suggests assignees from recent contributor history and optional capacity hints.
  • Practical outputs: Produces a scannable sprint plan with track tables, rationale for selections, warnings (cycles, overloads), and config status.

Quick Start

Generate a 14-day sprint plan from the open GitHub backlog with dependency detection, parallel tracks, and OKR/team alignment.

Frequently Asked Questions about pm-sprint-plan

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

FAQPage Schema
How do I create a two-week sprint plan from a GitHub issue backlog?

Sprint planning from a GitHub backlog involves reading full issue bodies, extracting acceptance criteria, detecting explicit and implicit file conflicts, and grouping executable tracks. This tool automates dependency detection and OKR alignment to output a defensible two-week sprint plan.

How does dependency detection work for GitHub issues during sprint planning?

Dependency detection builds directed graphs from explicit blockers and implicit file references in GitHub issues. It identifies cycle conflicts and scores root blockers by leverage to ensure parallel tracks remain executable without unresolved dependencies.

Can I align GitHub backlog issues with team capacity and OKRs for sprint planning?

Yes, sprint planning can align with OKRs and team capacity by parsing pm-config sections in GitHub issues. The tool scores issues by goal impact, boosts high-leverage root blockers, and suggests assignees from recent contributor history and optional capacity hints.

Do I need the GitHub CLI to prioritize backlog issues for sprint planning?

Yes, you need the GitHub CLI to read issue metadata required for sprint planning. The tool uses it to fetch open issues, parse pm-config sections for Team and OKRs, extract acceptance criteria, and build dependency graphs with cycle detection.

What is the best way to group independent work tracks for a sprint from GitHub issues?

Group independent work tracks by building a dependency graph from GitHub issues, scoring items against OKRs, and detecting parallelizable tasks. This tool automates grouping, orders tasks within each track, and suggests assignees from recent contributor history.

What happens if there are circular dependencies in my GitHub backlog during sprint planning?

When circular dependencies exist in your GitHub backlog, the tool's cycle detection flags them for manual resolution. The sprint plan output includes warnings for cycles and overloads alongside track tables and rationale for task selections.