Agent skill · product strategy · aiskillstore
agile-planning
Generate agile release plans with sprints and roadmaps using unique sprint codes. Use when creating sprint schedules, product roadmaps, release planning, or when user mentions agile planning, sprints, roadmap, or release plans.
Why this skill is useful
Generates structured agile release plans with unique sprint and task codes that streamline project management and tracking.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Agile Planning Generate lean agile release plans with sprint schedules and roadmaps. Overview This skill creates structured release plans for agile projects. It generates: Sprint schedules with unique codes (SPRINT-001, SPRINT-002, etc.) Tasks with ticket codes (T-001, T-002, etc.) for granular tracking Roadmaps showing timeline and milestones Dependencies and release checkpoints Use this when planning product releases, organizing work into sprints, or communicating timelines to stakeholders. Instructions Step 1: Gather Context Before generating a plan, collect: Project scope: What are we building? Timeline: How many weeks/months? Team size: Number of developers Sprint duration: Typically 2 weeks Key milestones: Alpha, beta, production dates Priorities: Must-have vs nice-to-have features Step 2: Structure Sprints Create sprints with: Unique codes: SPRINT-001, SPRINT-002, SPRINT-003 (sequential, zero-padded) Sprint theme: Descriptive name (e.g., "Payment Integration", "UI Polish") Duration: Start and end dates Goal: One-sentence sprint objective Tasks: 3-5 concrete tasks per sprint, each with unique ticket code (T-001, T-002, etc.) Dependencies: What blocks this sprint or depends on it Task Numbering: Use format: T-001, T-002, T-003 (zero-padded, sequential across entire release) Each task gets a unique code that persists throughout the project Never reuse task codes Sprint Duration Guidelines: 2 weeks (most common) = 10 working days Plan for 80% capacity (reserve 20% for meetings, bugs, unexpected) Balance workload across sprints Sprint Themes: Use clear, goal-oriented themes: Foundation, Setup, Infrastructure Core Features, MVP Development Integration, API Development Testing, Bug Fixes, Optimization Beta Launch, Production Release Step 3: Build Roadmap Group sprints into timeline view: By Quarter: Q1 2025, Q2 2025, etc. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/agile-planning