This skill should be used when the user asks to "create a roadmap", "plan a PoC", "build sprint plan", "execution timeline", "define prerequisites", or mentions proof of concept, MVP plan, milestones, sprint breakdown, go/no-go gates, or team composition. Generates 4-8 week execution roadmaps with sprint-level planning, prerequisite validation, measurable gate criteria, team composition, budget ranges, and risk registers. Use this skill whenever delivery planning or execution sequencing is needed, even if they don't explicitly ask for "roadmap-poc". [EXPLICIT]
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdreferences/roadmap-patterns.mdtemplates/output.docx.mdtemplates/output.htmlGenerates 4-8 week execution roadmaps with sprint-level planning, prerequisite validation, measurable go/no-go gate criteria, team composition, budget ranges, and risk registers. [EXPLICIT]
Un PoC sin kill criteria es un prototipo disfrazado de validacion. La planificacion de ejecucion no es un ejercicio de optimismo — es un acto de ingenieria donde cada sprint tiene entregables medibles, cada gate tiene criterios binarios (pasa/no pasa), y cada riesgo tiene un costo cuantificado.
The user provides a scope and duration as $ARGUMENTS. Parse $1 as the PoC/MVP scope, $2 as duration, $3 as team model. [EXPLICIT]
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso
{FORMATO}: markdown (default) | html | dual{VARIANTE}: ejecutiva (~40% — S1 kickoff + S5 timeline + S6 gates) | tecnica (full 7 sections, default)$ARGUMENTS format: [scope] [duration] [team-model]
Examples:
"loan-origination PoC 4 weeks" → scope=loan-origination, duration=4w, model=default
"full MVP 8 weeks distributed team" → scope=MVP, duration=8w, model=distributed
"infrastructure migration 6 weeks" → scope=infra, duration=6w, model=default
If reference materials exist, load them:
Read ${CLAUDE_SKILL_DIR}/references/roadmap-patterns.md
Day-by-day agenda:
| Activity | Owner | Duration | Outcomes |
|---|---|---|---|
| AS-IS Context Session | Tech Lead + PM | 2h | Current state documented |
| Definition of Done Workshop | Provider Lead + Stakeholders | 1.5h | DoD approved |
| Provider Setup (parallel) | Provider Ops | 3h | Infrastructure ready |
| Client Provisioning (parallel) | Client IT | 3h | Access & resources granted |
Parallel Setup Grid — two columns:
9+ prerequisites with owner, status, deadline, blocker flag. [EXPLICIT]
| ID | Prerequisite | Status | Owner | Deadline | Blocker |
|---|---|---|---|---|---|
| P1 | VPN / Dev environment access | ... | IT | ... | Yes |
| P2 | Source code repo & branch strategy | ... | Dev Lead | ... | Yes |
| P3 | CI/CD pipeline access | ... | DevOps | ... | Yes |
| P4 | Test environment provisioned | ... | Infra | ... | Yes |
| P5 | Stakeholder availability confirmed | ... | PM | ... | Yes |
| P6 | Architecture design approved | ... | Architect | ... | No |
| P7 | Data access / test data available | ... | Data team | ... | Yes |
| P8 | Security review scheduled | ... | Security | ... | No |
| P9 | Monitoring / alerting setup | ... | DevOps | ... | No |
Status chips: Complete | In Progress | Blocked | Not Started
Per sprint (2-week default):
Sprint N — [Target Feature/Capability]
Deliverables Checklist — each with specific, testable acceptance criteria.
Team Structure:
Budget Range (plus/minus 20%):
Week 0 Week 1-2 Week 3-4 Week 5+
PRE-SERVICE SPRINT 1 SPRINT 2 STABILIZE
Kickoff Foundation Integration Deploy
Gate 0>1: Readiness to Sprint 1
Gate 1>2: Readiness to Sprint 2
Gate 2>Production: Production Readiness
| Risk ID | Description | Probability | Impact | Delay (days) | Cost Impact | Mitigation | Owner |
|---|---|---|---|---|---|---|---|
| R1 | [Risk] | H/M/L | H/M/L | [N] | $[X] | [Plan] | [Who] |
Top 5-6 risks. Every risk includes estimated delay (days) and cost impact ($). This forces trade-off decisions: is mitigation investment justified?
| Scenario | Adaptation |
|---|---|
| No CI/CD infrastructure | Add 3-5 day setup task to Sprint 1 |
| 100% remote team | Add 15% communication overhead to ceremony estimates |
| Waterfall reporting required | Map each sprint to milestone gate; add formal gate documentation |
| Budget approved but team not hired | Insert 2-4 week recruitment phase before Week 0 |
| Multiple time zones (>4h spread) | Adjust ceremonies to UTC midpoint; record all sessions |
| Dimension | Option A | Option B | Decision Rule |
|---|---|---|---|
| Sprint length | 2 weeks (fast feedback, 5h/week ceremonies) | 3 weeks (less overhead, delayed detection) | 2 weeks for CI/CD teams; 3 weeks for teams <4 engineers |
| PoC scope | Narrow-deep (1 full flow) | Broad-shallow (3 partial flows) | Narrow-deep reduces risk; broad-shallow maximizes learning |
| Team capacity | Fixed (cost certainty) | Elastic (flexibility) | Fixed for PoC; elastic for long engagements |
| Pre-service | Full 5-day kickoff | Lightweight 2-day | Full for new teams; lightweight for teams with prior engagement |
IF team size <4 engineers → extend sprints to 3 weeks (reduce meeting-to-coding ratio)
IF critical prerequisite blocked at Week 0 → escalate with quantified delay cost ("Team waiting costs $X/day")
IF Sprint 1 gate fails → execute remediation sprint before Sprint 2 (skipping compounds defects)
IF budget >$500K → add PMO oversight and formal change control board
IF engagement >8 weeks → add mid-engagement retrospective and scope revalidation
Before delivering roadmap:
| Format | Default | Description |
|---|---|---|
markdown | Yes | Rich Markdown + Mermaid diagrams (Gantt). Token-efficient. |
html | On demand | Branded HTML (Design System). Visual impact. |
dual | On demand | Both formats. |
Default output is Markdown with embedded Mermaid Gantt diagrams. HTML generation requires explicit {FORMATO}=html parameter. [EXPLICIT]
Primary: RP-01_Roadmap_PoC_{project}.md (or .html if {FORMATO}=html|dual) — Pre-service kickoff, prerequisites validation, sprint breakdown, team composition, budget range, timeline, gate criteria, risk register.
Secondary: Gantt chart (Mermaid), parallel setup grid, prerequisites tracker, risk register spreadsheet.
Author: Javier Montano | Last updated: March 18, 2026
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.