What problem does it solve?
Release planning is often disjointed, with product goals disconnected from actionable feature lists, stakeholder-aligned roadmaps, and tracker artifacts. This leads to scope creep, misalignment, and delayed downstream work like feature specs and backlog tasks. The release-planner skill solves this by turning approved steering documentation into a prioritized, capacity-aligned feature list, published roadmap, and pre-created tracker epics ready for immediate use.
Core Features & Use Cases
- Capacity-aligned prioritization: Ranks candidate features using MoSCoW priority and T-shirt sizing against team capacity, with clear minimum, target, and stretch scope tiers to enforce 15% headroom and avoid overcommitment.
- Cross-platform roadmap publishing: Automatically publishes a structured release plan page to Confluence, Notion, ADO Wiki, or local files for stakeholder review and alignment.
- Tracker epic pre-creation: Creates empty, properly tagged epics in JIRA, Linear, Azure DevOps, or local tracker systems for each in-scope feature, so downstream skills can immediately link specs and tasks without manual setup.
- Use Case: A product team preparing for an MVP launch can use this skill to turn steering docs into an approved feature shortlist, share a roadmap with stakeholders, and create JIRA epics for each feature so engineers can start writing specs the same day.
Quick Start
Use the release-planner skill to plan the Q3 2025 release by prioritizing features from the approved steering docs, publishing a roadmap to Confluence, and creating JIRA epics for each in-scope feature.
