// This skill should be used when the user asks to "create a delivery plan", "build a roadmap", "plan the phases", "define milestones", "map the critical path", "estimate the timeline", or needs a structured phased plan for delivering an initiative.
| name | Delivery Plan and Roadmap |
| description | This skill should be used when the user asks to "create a delivery plan", "build a roadmap", "plan the phases", "define milestones", "map the critical path", "estimate the timeline", or needs a structured phased plan for delivering an initiative. |
| version | 1.0.0 |
Produce a realistic, phased delivery plan with milestones, dependencies, and a critical path analysis. Ground estimates in scope and team capacity, not wishful thinking.
A delivery plan is not a Gantt chart — it is a set of commitments backed by explicit assumptions about scope, team, and risk. This skill produces a plan that delivery teams can execute and sponsors can track.
Structure the delivery into phases where each phase delivers standalone business value:
| Phase | Name | Objective | Duration | Entry Criteria | Exit Criteria |
|---|---|---|---|---|---|
| 0 | Foundations | Enable delivery | 2 weeks | Kick-off complete | Environments ready |
| 1 | MVP | Core capability live | 6 weeks | Phase 0 exit criteria met | P0 features in production |
| 2 | Enhancement | Full feature set | 8 weeks | Phase 1 exit criteria met | All MoSCoW Must Haves live |
For each phase, define:
Map dependencies between work streams:
Dependency table:
| Dependency | Type | Provider | Required by | Risk if Late |
|---|---|---|---|---|
| [item] | Internal/External/Regulatory | [who] | [date/milestone] | [impact] |
Identify the longest chain of dependent tasks — this is the critical path. Delays on the critical path delay the project; delays off the critical path may have float.
Produce a simple critical path diagram:
Phase 0 (2w) → Phase 1 API (3w) → Phase 1 Frontend (3w) → Phase 1 Go-Live
↗ (Phase 1 API must complete first)
Phase 1 Data Migration (4w) — CRITICAL PATH
| Risk | Likelihood | Impact | Risk Score | Mitigation | Owner |
|---|---|---|---|---|---|
| [risk] | H/M/L | H/M/L | H/M/L | [action] | [name] |
Flag critical path risks specifically — these are the ones that will delay the whole programme.
| Role | Phase 1 | Phase 2 | Phase 3 |
|---|---|---|---|
| Tech Lead | 1 FTE | 1 FTE | 0.5 FTE |
| Engineers | 2 FTE | 3 FTE | 2 FTE |
| QA | 0.5 FTE | 1 FTE | 1 FTE |
Produce:
Week 1: X | Week 3: Y | Week 6: Z)references/estimation-techniques.md — T-shirt sizing, story points, and reference class forecastingassets/delivery-plan-template.md — Blank delivery plan templateThis skill should be used when the user asks to "use the VAMFI templates", "get the proposal template", "find the PRD template", "use the HLD template", "load the runbook template", "access artifact templates", or needs a blank template for any VAMFI consultancy document.
This skill should be used when the user asks to "shape stories", "create a backlog", "break this epic into stories", "write user stories with acceptance criteria", "define the product backlog", "estimate stories", or needs to convert a PRD or delivery plan into an executable sprint backlog.
This skill should be used when the user asks to "implement this feature", "write the code for this story", "execute this implementation plan", "make this code change", "add this functionality", or needs hands-on code implementation following a VAMFI implementation plan.
This skill should be used when the user asks to "review this code", "review the PR", "check code quality", "refactor this module", "improve this code", "run a code review", or needs systematic review of recently written or changed code before it merges.
This skill should be used when the user asks to "optimise costs", "reduce cloud spend", "improve performance", "fix slow queries", "analyse FinOps", "reduce latency", "optimise infrastructure", "right-size resources", or needs to improve the efficiency of a running system.
This skill should be used when the user asks to "assess the current architecture", "document the existing system", "analyse the codebase", "identify technical debt", "review the legacy system", "produce a current-state report", or needs to understand what exists before designing a target architecture.