From pdm-release-planning
Select and design the right rollout strategy for a release — balancing speed, risk, and user impact.
npx claudepluginhub devmuslim/pdm-skills --plugin pdm-release-planningThis skill uses the workspace's default tool permissions.
Select and design the right rollout strategy for a release — balancing speed, risk, and user impact.
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.
Select and design the right rollout strategy for a release — balancing speed, risk, and user impact.
Ask for:
Description: Deploy to 100% of users at once. Best for: Low-risk changes, internal tools, hotfixes, small user bases. Risk: High — if something breaks, everyone is affected. Rollback: Redeploy previous version.
Description: Release to 5% → 25% → 50% → 100% over days/weeks. Best for: B2C products, large user bases, medium-risk features. Risk: Medium — issues caught early affect small % of users. Rollback: Reduce percentage to 0%.
Description: Release to a small "canary" group (e.g., internal employees or power users) before general availability. Best for: High-risk features, new infrastructure, major architecture changes. Risk: Low — issues are caught before wide exposure. Rollback: Simple — revert canary group.
Description: Deploy code to all users but hide behind a flag. Enable selectively. Best for: When you want zero-downtime deploys and gradual enablement. Risk: Low — can toggle off instantly. Rollback: Disable flag (seconds).
Description: Run two identical environments; switch traffic from Blue (old) to Green (new). Best for: Zero-downtime deployments, critical infrastructure. Risk: Low — instant rollback by switching back to Blue. Rollback: Redirect traffic to Blue (seconds).
| Context | Recommended Strategy |
|---|---|
| Low risk, small user base | Big Bang |
| Medium risk, large B2C | Phased Rollout |
| High risk, unknown stability | Canary + Feature Flags |
| Critical infrastructure | Blue/Green |
| Gradual feature adoption | Feature Flags |
Based on selected strategy, produce:
Phased Rollout Example:
| Phase | % Users | Duration | Success Criteria | Rollback Trigger |
|---|---|---|---|---|
| Phase 1 | 5% | 24 hours | Error rate < 0.5%, p95 latency < 300ms | Error rate > 1% |
| Phase 2 | 25% | 48 hours | Same + no P0 bugs | Any P0 bug |
| Phase 3 | 100% | — | Stable for 72 hours | — |
/launch-checklist or /assess-readiness