codexkit-sprint-planning-assistant

Convert a groomed backlog into a sprint plan aligned to capacity and velocity.

21|12|Updated Mar 20, 2026

Search Tags:#planning #dependencies #backlog #velocity #sprint #capacity

Ready to run

npx skills add https://github.com/hoavdc/CodexKit --skill codexkit-sprint-planning-assistant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codexkit-sprint-planning-assistant
Source: https://github.com/hoavdc/CodexKit/tree/main/skills/codexkit-sprint-planning-assistant
Command: npx skills add https://github.com/hoavdc/CodexKit --skill codexkit-sprint-planning-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes a groomed backlog into a clearly scoped sprint plan, aligning scope with team capacity and velocity.

Core Features & Use Cases

Backlog-to-sprint translation: converts prioritized items into a runnable sprint with estimates and owners.
Dependency and risk management: identifies blockers and cross-team dependencies that affect commitment.
Sprint goal and deliverables: generates a one-sentence sprint goal and a stakeholders-ready summary.

Quick Start

Feed backlog items, capacity, velocity, and sprint horizon into the skill to generate a ready-to-run sprint plan.

Frequently Asked Questions about codexkit-sprint-planning-assistant

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

FAQPage Schema

How do I turn a groomed backlog into a sprint plan aligned with team velocity?▼

Sprint planning converts prioritized backlog items into a runnable sprint by matching estimated effort and dependencies against known capacity and last-sprint velocity to determine a safe commitment.

What inputs do I need to generate a sprint-ready plan from my backlog?▼

Generating a sprint-ready plan requires backlog items with descriptions and acceptance criteria, known team capacity, last-sprint velocity, and a defined 1- or 2-week sprint horizon.

How does backlog-to-sprint planning handle cross-team dependencies and blockers?▼

Backlog-to-sprint planning identifies blockers and cross-team dependencies during scope alignment, ensuring that risk factors affecting the final sprint commitment are explicitly managed.

Can I use this sprint planning approach for a two-week sprint cycle?▼

Yes, this sprint planning approach explicitly supports both 1- and 2-week sprint horizons, adjusting scope and estimates to fit the selected cycle duration and team capacity.

What is the best way to create a sprint goal and stakeholder summary from backlog items?▼

Translating a groomed backlog into a sprint plan automatically generates a one-sentence sprint goal and a stakeholders-ready summary alongside the assigned estimates and owners.

Why does my sprint commitment fail to align with actual team capacity?▼

Sprint commitments fail when backlog planning ignores last-sprint velocity or capacity constraints, making it necessary to map estimated effort against these metrics for a safe commitment.