From pdm-release-planning
Calculate the right time buffer for a release based on delivery complexity, team history, and risk profile — so timelines are honest and defensible.
npx claudepluginhub devmuslim/pdm-skills --plugin pdm-release-planningThis skill uses the workspace's default tool permissions.
Calculate the right time buffer for a release based on delivery complexity, team history, and risk profile — so timelines are honest and defensible.
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.
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.
Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.
Calculate the right time buffer for a release based on delivery complexity, team history, and risk profile — so timelines are honest and defensible.
Score each factor 1 (low) to 3 (high):
| Factor | 1 — Low | 2 — Medium | 3 — High | Your Score |
|---|---|---|---|---|
| Technical complexity | Known tech, small changes | Some new patterns | New architecture, integrations | |
| Team experience | Team has done this before | Mixed experience | New team or new domain | |
| Dependency count | 0–2 dependencies | 3–5 dependencies | 6+ dependencies | |
| External dependencies | None | 1–2 external | 3+ external (vendors, App Store) | |
| Requirement stability | Fully defined | Some unknowns | Frequently changing | |
| Team size | 1–3 people | 4–8 people | 9+ people |
Total Score: X / 18
| Total Score | Buffer | Rationale |
|---|---|---|
| 6–9 | 10% | Low complexity, high confidence |
| 10–13 | 20% | Moderate risk, manageable unknowns |
| 14–16 | 30% | High complexity or dependency risk |
| 17–18 | 40%+ or split release | Too risky to commit as single release |
Example:
"Our engineering estimate is 6 weeks. Based on the integration complexity and external vendor dependency, we're committing to 7.5 weeks, which gives us a target date of [date]. This is the date we're confident delivering to, not a worst-case."
Never call it "padding." Call it "delivery confidence buffer."
/milestone-plan