Skill

Skill: milestone-plan

Convert release scope and dependencies into a structured milestone plan with owners, dates, and buffer recommendations.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-release-planning

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Convert release scope and dependencies into a structured milestone plan with owners, dates, and buffer recommendations.

SKILL.md

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

startup-financial-modeling

Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.

startup-business-analyst

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: milestone-plan

Purpose

Convert release scope and dependencies into a structured milestone plan with owners, dates, and buffer recommendations.

When to Use

After scope and dependencies are defined
When creating a release timeline for stakeholders
When managing a multi-team delivery

Framework: Milestone Planning

Step 1 — Gather Inputs

Ask for:

Release scope (Must Haves from release-scope)
Team size and sprint length
Known constraints (holidays, freeze periods, external deadlines)
Target release date

Step 2 — Define Milestone Types

Type	Purpose
Design Complete	All UX/specs signed off, ready for development
Development Complete	All Must Have features merged to main
Code Freeze	No new features; only bug fixes allowed
QA Complete	All P0/P1 bugs resolved, regression passed
UAT Sign-off	Business approval received
Release Candidate	Build ready for production
Go-Live	Production deployment
Stabilization End	Monitoring period complete, team stands down

Step 3 — Milestone Table

#	Milestone	Target Date	Owner	Dependencies	Status
M1	Design Complete	Week 1	Design Lead	Requirements finalized	⬜ Pending
M2	Dev Complete	Week 3	Tech Lead	M1 + D1	⬜ Pending
M3	Code Freeze	Week 4	PDM	M2	⬜ Pending
M4	QA Complete	Week 5	QA Lead	M3	⬜ Pending
M5	UAT Sign-off	Week 5	Business Owner	M4	⬜ Pending
M6	Go-Live	Week 6	PDM + DevOps	M5	⬜ Pending

Step 4 — Buffer Recommendation

Based on risk register score:

Low risk (score < 15): Add 10% buffer
Medium risk (score 15–30): Add 20% buffer
High risk (score > 30): Add 30% buffer or split release

Step 5 — Text-Based Timeline

Week 1  ████ Design Complete
Week 2  ████████ Dev Sprint 1
Week 3  ████████ Dev Sprint 2 → Dev Complete
Week 4  ████ Code Freeze | QA Begins
Week 5  ████████ QA Complete → UAT Sign-off
Week 6  ██ Go-Live → Stabilization

Output Format

Milestone table with owners and dates
Buffer recommendation with rationale
Text timeline
Suggested next command: /launch-checklist or /assess-readiness