skills.rest
OntoLedgy
OntoLedgyOFFICIAL
Explore all skills by this author →
GitHub

sprint-planner

Plan executable sprints by ordering prioritized tickets into dependency-aware waves.

Updated Aug 23, 2026
Search Tags:#agile#sprint planning#capacity planning#backlog management#dependency ordering#tracker integration#kickoff document
One-click install
npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill sprint-planner-ontoledgy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-planner
Source: https://github.com/OntoLedgy/ol_ai_context_library/tree/main/skills/sprint-planner
Command: npx skills add https://github.com/OntoLedgy/ol_ai_context_library --skill sprint-planner-ontoledgy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually planning sprints often leads to missed task dependencies, capacity overallocation, and misaligned engineer assignments, causing delays and wasted effort during software delivery cycles.

Core Features & Use Cases

  • Dependency-Aware Wave Ordering: Automatically topologically sorts tickets into parallel execution waves based on explicit, file-level, and data-model dependencies.
  • Capacity-Constrained Scope Fitting: Matches selected ticket estimates to sprint capacity, with automatic cut proposals for over-scoped backlogs that never break partial requirements.
  • Multi-Platform Integration: Natively supports Jira, Linear, Azure DevOps, and local ticket tracking, plus Confluence, Notion, ADO Wiki, and local documentation for kickoff publishing.
  • Use Case: A tech lead preparing a 2-week sprint for a payment processing feature epic can use this skill to pull relevant tickets, assign them to the correct engineer skill, generate a compliant kickoff document, and update all tracking systems in minutes without manual spreadsheet work.

Quick Start

Use the sprint-planner skill to create a 10-day sprint plan for the Q4 payment processing epic, fitting 42 engineer-hours of work and publishing the kickoff document to Confluence.

Frequently Asked Questions about sprint-planner

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

FAQPage Schema
How do I automatically order backlog tickets into dependency-aware sprint waves?▼

Sprint planning can automatically topologically sort backlog tickets into parallel execution waves using explicit, file-level, and data-model dependencies to prevent execution delays. This dependency-aware wave ordering ensures tasks are sequenced correctly for engineers.

How do I fit backlog tickets to team capacity without breaking partial requirements?▼

Capacity-constrained scope fitting matches selected ticket estimates to available sprint capacity and generates automatic cut proposals for over-scoped backlogs. These automatic cuts never break partial requirements, ensuring deliverables remain intact when capacity is limited.

Does sprint planning work with Jira, Linear, and Azure DevOps for backlog management?▼

Yes, sprint planning natively supports backlog management and tracker integration with Jira, Linear, Azure DevOps, and local ticket tracking. It pulls prioritised tickets, updates the tracker with new sprints, and generates a standardised kickoff document across these platforms.

Can I publish a sprint kickoff document to Confluence, Notion, or ADO Wiki?▼

Yes, sprint planning generates a standardised kickoff document and publishes a sprint overview page directly to Confluence, Notion, ADO Wiki, or local documentation. This automates sprint kickoff publishing alongside tracker updates for centralized team alignment.

What is the best way to replan a sprint mid-cycle when dependencies change?▼

Mid-sprint replanning handles dependency changes by reordering prioritised tracker tickets into updated execution waves and matching scope to remaining team capacity. It applies the same dependency-aware logic used for initial sprint planning to adjust scope dynamically.

How do I convert an epic backlog into an executable sprint plan for a specific feature?▼

Backlog-to-plan conversion pulls relevant tickets from an epic, assigns them to engineer skills, and fits ticket estimates to sprint capacity like 42 engineer-hours. It generates a kickoff document and updates tracking systems without manual spreadsheet work.

Related Skills

Explore More Software Engineering Skills→
russosalvrussosalv
5

spec-to-workitem

Translate NONoise sprint manifest macro tasks into external issue tracker work items.

Community
Advanced
easingthemeseasingthemes
6

dx-doc-gen

Generate wiki documentation from spec files and publish to ADO Wiki or Confluence.

Community
Advanced
dipandhali2021dipandhali2021

sprint-planning

Plan sprints with capacity, priorities, dependencies, and risk analysis.

Community
Advanced
warpcodewarpcode
2

pm-project-analyser

Break down project concepts into epics and plan sprints by capacity.

Community
Intermediate