skills.rest
krystophny
krystophnyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sprint-plan

Consolidate and prioritize GitHub issues into a sprint backlog via the GitHub API.

Updated Aug 27, 2026
Search Tags:#planning#architecture#backlog#sprint#github-api#issue-consolidation#meta-issues
One-click install
npx skills add https://github.com/krystophny/prompts --skill sprint-plan-krystophny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/krystophny/prompts/tree/main/skills/sprint-plan
Command: npx skills add https://github.com/krystophny/prompts --skill sprint-plan-krystophny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strategic sprint planning to consolidate issues, update meta-issues, and establish sprint goals using the chris-architect role. Use after PLAY phase or when planning the next sprint to align team priorities and architectural direction.

Core Features & Use Cases

  • Issue consolidation and duplicate removal to clean backlogs.
  • Meta-issue updates for SPRINT BACKLOG and DESIGN to reflect current priorities.
  • Sprint goal establishment with Definition of Done and architectural considerations.

Quick Start

Provide the latest PLAY findings to chris-architect and generate a consolidated sprint plan.

Frequently Asked Questions about sprint-plan

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

FAQPage Schema
How do I consolidate duplicate issues into a sprint backlog using the GitHub API?▼

Sprint backlog consolidation analyzes existing GitHub issues to identify duplicates and removes them, creating a compact, prioritized list of actionable items for your next sprint.

How do I establish sprint goals with a Definition of Done for architectural planning?▼

Sprint goal establishment integrates architectural considerations and a clear Definition of Done directly into your planning process, ensuring evidence-based priorities are recorded within meta-issues.

Does sprint planning via the GitHub API perform any git operations or branch merges?▼

No, sprint planning via the GitHub API operates exclusively on issue tracking to update meta-issues and identify defects, enforcing strict planning rules without performing any git operations.

When should I update SPRINT BACKLOG and DESIGN meta-issues for the next sprint?▼

Update SPRINT BACKLOG and DESIGN meta-issues immediately after your PLAY phase findings are ready, aligning team priorities and architectural direction before the next sprint begins.

Can I use PLAY findings to identify actionable defects for sprint planning?▼

Yes, PLAY findings serve as the primary input to identify actionable defects, allowing the chris-architect role to generate a consolidated sprint plan based on evidence.

Why are evidence-based priorities enforced during sprint backlog consolidation?▼

Evidence-based priorities are enforced to ensure sprint planning decisions are strictly backed by PLAY findings and architectural requirements, recording all decisions transparently within meta-issues.

Related Skills

Explore More Product & Management Skills→
lane2077lane2077

session-init

Initialize Claude Code sessions by checking environment and summarizing task state.

Community
Intermediate
kanitmann01kanitmann01

project-manager

Plan and track team tasks with owners and acceptance criteria.

Community
Intermediate
michsindlingermichsindlinger
1

backlog-organization

Organize product backlogs with MoSCoW prioritization and sprint planning.

Community
Intermediate
markus41markus41
1

scrum

Facilitate Scrum ceremonies and manage sprint backlog with agile estimation.

Community
Basic