prompt

Analyze GitHub issues to assess complexity and tier them for Claude Code sprint planning prompts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue triage and sprint planning can be time-consuming and error-prone. This Skill analyzes one or more issues to assess complexity, classify a suitable effort tier, and generate a ready-to-use thread prompt with model and resource guidance.

Core Features & Use Cases

  • Analyze multiple issues to derive per-issue complexity signals and a batch tier.
  • Produce a copy-paste-ready prompt per issue or per batch, including ACs, dependencies, labels, and suggested files.
  • Support PM-driven planning with optional subagent partitioning for scalable threads.

Quick Start

Provide a batch of issue numbers to generate tiered thread prompts you can paste into Claude Code.

Frequently Asked Questions about prompt

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

FAQPage Schema
How do I analyze GitHub issues for sprint planning and complexity tiering?

You can analyze GitHub issues by parsing issue bodies, labels, milestones, and comments to extract acceptance criteria and dependencies, then classifying them into a suitable effort tier for sprint planning.

How do I generate a copy-paste-ready prompt from GitHub issues for Claude Code?

Generating a Claude Code thread prompt from GitHub issues requires extracting acceptance criteria, dependencies, and suggested files, then formatting the output into a ready-to-use prompt with model and effort recommendations.

Can I batch analyze multiple GitHub issues to get a single effort tier for sprint planning?

Yes, batch analyzing multiple GitHub issues derives per-issue complexity signals and an overall batch tier, producing a single copy-paste-ready prompt that guides code reviews and sprint planning for the entire batch.

What is the best way to turn GitHub issue acceptance criteria into actionable code review plans?

Turning GitHub issue acceptance criteria into code review plans involves analyzing issue bodies and comments to identify dependencies and potential CR plans, then formatting them into a structured prompt for Claude Code threads.

Does sprint planning with GitHub issues support subagent partitioning for scalable Claude Code threads?

Sprint planning with GitHub issues supports optional subagent partitioning, allowing PM-driven planning to scale by generating multiple Claude Code thread prompts partitioned across subagents for parallel execution.