PMO governance backbone — portfolio tracking, phase gate management, resource orchestration, dependency control, and proposal QA validation across the entire discovery pipeline. Use when the user asks to "track the discovery", "manage the portfolio", "validate the proposal", "run governance check", "check phase dependencies", "coordinate resources", or mentions PMO, program management, portfolio governance, phase gates, proposal readiness, milestone tracking, or cross-phase dependency management. Works as the structural glue that holds the entire discovery pipeline together — from Phase 0 through Handover.
From pmnpx claudepluginhub javimontano/mao-pm-apexThis skill is limited to using the following tools:
examples/README.mdexamples/sample-output.htmlexamples/sample-output.mdprompts/prompt.mdSearches, 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.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
Structural governance layer that manages the discovery pipeline as a formal program — tracking phases, gates, resources, dependencies, risks, and proposal readiness. Operates as the connective tissue between all 48 skills, ensuring nothing falls through cracks, phases don't skip prerequisites, and the final proposal is validated before client delivery.
El descubrimiento sin gobernanza es improvisación disfrazada de metodología. Este skill impone la disciplina de programa sobre el pipeline: cada fase tiene prerequisites, cada gate tiene criteria, cada entregable tiene owner y fecha. No es burocracia — es la diferencia entre "hicimos un discovery" y "ejecutamos un programa de discovery confiable."
Governance ≠ Burocracia. El gobierno existe para habilitar velocidad con confianza, no para frenar. Cada control debe justificar su existencia con un riesgo que mitiga.
Trazabilidad Total. Cada decisión, cambio de alcance, riesgo materializado, y dependencia resuelta queda registrada. El programa se puede auditar en cualquier momento.
Proposal QA = Quality Gate Final. La propuesta v1 no sale hasta que pasa una validación multidimensional que verifica coherencia técnica, viabilidad, completitud, y alineación con hallazgos del discovery.
Parse $1 as project/program name. Detect discovery context from repo.
Parameters:
{MODO}: piloto-auto (default) | desatendido | supervisado | paso-a-paso
{FORMATO}: markdown (default) | html | dual{VARIANTE}: ejecutiva (~40%) | técnica (full, default)| Phase | Prerequisites | Gate | Gate Criteria | Owner |
|---|---|---|---|---|
| Phase 0: Stakeholder Mapping | Project kickoff | — | Map complete, power grid populated | Domain Analyst |
| Phase 1: AS-IS | Phase 0 complete | — | 10-section analysis delivered | Technical Architect |
| Phase 2: Flow Mapping | Phase 1 complete | — | Domain taxonomy + 8-12 flows | Domain Analyst |
| Phase 3: Scenarios | Phase 2 complete | G1 | Scenario approved by committee | Full-Stack Generalist |
| Phase 3b: Feasibility | G1 passed | 3b checkpoint | Feasibility verdict + viability scorecard | Quality Guardian |
| Phase 4: Roadmap + Cost | Phase 3b passed | — | Roadmap + cost drivers delivered | Delivery Manager |
| Phase 4b: Commercial Model | Phase 4 complete | G2 | Commercial structure approved | Data Strategist |
| Phase 5a: Functional Spec | G2 passed | — | Spec complete + use cases validated | Technical Architect |
| Phase 5b: Executive Pitch | G2 passed | G3 | Pitch approved, investment case clear | Change Catalyst |
| Phase 6: Handover | G3 passed | — | Handover package complete | Delivery Manager |
Diagrama requerido: Gantt chart (Mermaid) con timeline del programa completo, gates como milestones
Para cada quality gate, evalúa:
Gate Evaluation Protocol:
GATE EVALUATION: {gate_name}
════════════════════════════
Phase Completing: {phase}
Date: {date}
ENTRY CRITERIA:
[ ] {criterion_1} — {status: ✅/⚠️/🔴}
[ ] {criterion_2} — {status}
...
DELIVERABLES CHECK:
[ ] {deliverable_1} — {completeness: complete/partial/missing}
[ ] {deliverable_2} — {completeness}
EVIDENCE CHAIN:
- {deliverable} → {finding} → {implication for next phase}
DEPENDENCIES RESOLVED:
[ ] {dependency_1} — {status}
RISKS CARRIED FORWARD:
- {risk_1}: {mitigation status}
VERDICT: PASS / CONDITIONAL PASS / FAIL
Conditions (if conditional):
1. {condition}
2. {condition}
Fail reasons (if fail):
1. {reason} → {remediation}
| Expert | Current Phase | % Allocated | Bottleneck Risk | Next Phase Needed |
|---|---|---|---|---|
| Technical Architect | Phase 1 | 100% | 🟡 Phase 3 needs same expert | Phase 3 (50%) |
| Domain Analyst | Phase 0 | 80% | 🟢 Available for Phase 2 | Phase 2 (100%) |
Diagrama requerido: Flowchart (Mermaid) mostrando flujo de recursos entre fases
| Source Phase | Output | Consumer Phase | Contract | Status |
|---|---|---|---|---|
| Phase 1: AS-IS | Stack inventory | Phase 3b: Feasibility | technology_inventory.json | ✅ Delivered |
| Phase 2: Flow Mapping | Domain taxonomy | Phase 4: Cost | scope_decomposition base | ⚠️ Pending |
| Phase 3: Scenarios | Approved scenario | Phase 3b: Feasibility | scenario_claims.json | ⚠️ In Progress |
Diagrama requerido: Sequence diagram (Mermaid) mostrando flujo de datos entre fases
SECCIÓN CRÍTICA — el validador final antes de que la propuesta llegue al cliente.
La Propuesta v1 se construye de los outputs de Phases 4-5b. Antes de enviar al cliente, pasa por una validación multidimensional:
Trazabilidad de Fallas QA → Fase Origen: Si una dimensión QA falla, la remediación se traza directamente a la(s) fase(s) responsable(s):
5a. Coherencia Técnica
5b. Completitud
5c. Viabilidad de Propuesta
5d. Alineación con Hallazgos
PROPOSAL QA SCORECARD
═════════════════════
Proyecto: {nombre}
Propuesta v1 — Validación Pre-Envío
| Dimensión | Score | Hallazgos | Acción |
|---|---|---|---|
| Coherencia Técnica | [X]/5 | {findings} | {action if <4} |
| Completitud | [X]/5 | {findings} | {action if <4} |
| Viabilidad | [X]/5 | {findings} | {action if <4} |
| Alineación | [X]/5 | {findings} | {action if <4} |
COMPOSITE: [X.X]/5.0
VEREDICTO: APROBADA / APROBADA CON CONDICIONES / RECHAZADA
Threshold mínimo: 3.5/5.0 composite, ninguna dimensión <3
Condiciones (si aplica):
1. {condición}
LISTA PARA ENVÍO A CLIENTE: SÍ / NO
| Phase | Status | Planned End | Actual/Forecast | Variance | RAG |
|---|---|---|---|---|---|
| Phase 0 | ✅ Complete | Day 2 | Day 2 | 0 | 🟢 |
| Phase 1 | 🔄 In Progress | Day 5 | Day 6 (forecast) | +1 day | 🟡 |
| Phase 3b | ⏳ Not Started | Day 10 | — | — | ⚪ |
Diagrama requerido: Timeline/Gantt (Mermaid) con estado actual del programa
El project manager es el backbone de governance que acompaña TODOS los prompts. Se activa implícitamente en cada ejecución de prompt.
| Prompt | Rol del PM | Sección Activada |
|---|---|---|
00-plan-discovery | Co-autor: Program Charter | S1 (Charter) |
01-stakeholder-map | Receptor: RACI para tracking | S3 (Resources) |
02-brief-tecnico | Monitor: phase status update | S6 (Dashboard) |
03-asis-analysis | Monitor: dependency tracking | S4 (Dependencies) |
04-mapeo-flujos | Monitor: data contract validation | S4 (Dependencies) |
05-escenarios | Gate evaluator: G1 | S2 (Gate Management) |
06-solution-roadmap | Gate evaluator: G2, scope tracking | S2 + S4 |
07-spec-funcional | Monitor: completeness tracking | S6 (Dashboard) |
08-pitch-ejecutivo | QA validator: proposal coherence | S5 (Proposal QA) |
09-handover | Gate evaluator: G3, final QA | S2 + S5 + S7 |
revisar | Executor primario: full QA audit | S5 (Proposal QA) |
evolucionar | Re-validator: post-improvement QA | S5 + S6 |
rescatar | Triage: gate status assessment | S2 + S6 |
| Dominio | Skills | Cantidad |
|---|---|---|
| Discovery Pipeline | discovery-orchestrator, stakeholder-mapping, workshop-facilitator, asis-analysis, dynamic-sme, flow-mapping, scenario-analysis, technical-feasibility, software-viability, solution-roadmap, cost-estimation, commercial-model, functional-spec, executive-pitch, discovery-handover, mermaid-diagramming | 16 |
| Architecture Design | software-architecture, architecture-tobe, enterprise-architecture, solutions-architecture, infrastructure-architecture, devsecops-architecture, design-system, functional-toolbelt | 8 |
| Data Strategy | data-science-architecture, bi-architecture, data-engineering, database-architecture, data-governance, data-quality, analytics-engineering | 7 |
| Cloud & Mobile | cloud-native-architecture, cloud-migration, mobile-architecture, mobile-assessment | 4 |
| Engineering Excellence | api-architecture, event-architecture, security-architecture, performance-engineering, observability | 5 |
| Consulting & Quality | quality-engineering, testing-strategy, user-representative | 3 |
| Governance & Risk | project-program-management, risk-controlling-dynamics | 2 |
| Delivery & Brand | html-brand, ux-writing, roadmap-poc | 3 |
| TOTAL | 48 |
Todos los 48 skills tienen examples/ con:
sample-output.md — Output markdown de referencia (Acme Corp Banking Modernization)sample-output.html — Output HTML branded (Design System CSS)README.md — Índice de assetsUbicación: plugins/metodologia-discovery-framework/skills/{skill-name}/examples/
| Decision | Enables | Constrains | When to Use |
|---|---|---|---|
| Full governance (all sections) | Maximum confidence, auditable | Overhead en programas pequeños | Discovery >3 phases, high-stakes |
| Lite governance (S1+S2+S5) | Fast tracking | Pierde trazabilidad detallada | Discovery ≤3 phases, fast-track |
| QA-only (S5) | Focused proposal validation | No tracking history | When proposal exists, need validation |
| Gate-only (S2) | Phase transition control | No resource or dependency tracking | Simple sequential pipeline |
| Scenario | Response |
|---|---|
| Discovery runs out of order (phase skip) | Flag as governance violation. Document rationale. Assess impact on downstream phases |
| Scope change mid-discovery | Impact assessment across all remaining phases. Re-estimate if >10% scope change |
| Expert unavailable for gate review | Designate alternate. If no alternate, escalate with documented risk |
| Proposal QA fails multiple dimensions | Do NOT send to client. Identify remediation per dimension. Re-run QA after fixes |
| Client requests deliverables before QA | Flag risk. Offer "draft" watermark. Never mark as final pre-QA |
| Pipeline variant = Quick Reference | Adapt to 3-phase subset. QA still mandatory for proposal |
graph TD
subgraph Core
PPM[Project & Program Management]
end
subgraph Inputs
I1[Discovery Pipeline Context] --> PPM
I2[Phase Deliverables] --> PPM
I3[Expert Committee] --> PPM
I4[Scope Baseline] --> PPM
end
subgraph Outputs
PPM --> O1[Program Charter]
PPM --> O2[Gate Evaluations]
PPM --> O3[Resource Tracking]
PPM --> O4[Dependency Matrix]
PPM --> O5[Proposal QA Scorecard]
PPM --> O6[Status Dashboard]
PPM --> O7[Lessons Learned]
end
subgraph Related Skills
RS1[risk-controlling-dynamics] -.-> PPM
RS2[pipeline-governance] -.-> PPM
RS3[discovery-orchestrator] -.-> PPM
RS4[discovery-handover] -.-> PPM
RS5[cost-estimation] -.-> PPM
end
Formato MD (default):
# Program Governance: {project_name}
## S1: Program Charter & Governance Framework
### Scope | Decision Rights | Communication | Phase Dependencies (Gantt)
## S2: Phase Gate Management
### Gate Protocol | G1 | 3b Checkpoint | G2 | G3
## S3: Resource & Capacity Orchestration
### Allocation Table | Bottlenecks | Skill Gaps (Flowchart)
## S4: Cross-Phase Dependency Control
### I/O Matrix | Data Contracts | Scope Change Log (Sequence Diagram)
## S5: Proposal QA Validation
### Coherencia | Completitud | Viabilidad | Alineacion | Scorecard
## S6: Status Reporting & Dashboard
### RAG | Milestones | Risk Burn-Down | Decision Log
## S7: Governance & Lessons Learned
Formato DOCX: Reporte formal de gobernanza PMO: charter con firmas, evaluaciones de gate documentadas, scorecard de propuesta con trazabilidad a fase origen, dashboard de estado con graficos de tendencia, y log de decisiones auditable.
Formato XLSX (bajo demanda):
{fase}_project_program_management_{cliente}_{WIP}.xlsxFormato PPTX (bajo demanda):
{fase}_project_program_management_{cliente}_{WIP}.pptx| Dimension | Peso | Criterio (7/10 minimo) |
|---|---|---|
| Trigger Accuracy | 10% | Se activa ante keywords de PMO, governance, portfolio, gate, proposal QA; no ante PM generico de proyectos |
| Completeness | 25% | Las 7 secciones cubren charter, gates, recursos, dependencias, QA, dashboard, y retrospectiva |
| Clarity | 20% | Gate criteria son binarios (PASS/CONDITIONAL/FAIL); QA scorecard tiene threshold numerico claro |
| Robustness | 20% | Edge cases (phase skip, scope change, expert unavailable, multi-dimension QA fail) tienen protocolo |
| Efficiency | 10% | Variante ejecutiva y modos operacionales permiten activacion parcial sin perder trazabilidad |
| Value Density | 15% | Cada gate produce veredicto accionable; QA fallas se trazan a fase origen con plan de remediacion |
Umbral minimo: 7/10 en cada dimension. Composite ponderado >= 7.0 para considerar el output aceptable.
| Format | Default | Description |
|---|---|---|
markdown | Yes | Rich Markdown + Mermaid diagrams. Token-efficient. |
html | On demand | Branded HTML (Design System). Visual impact. |
dual | On demand | Both formats. |
Default output is Markdown with embedded Mermaid diagrams. HTML generation requires explicit {FORMATO}=html parameter.
Primary: P-01_Program_Governance_{project}.md (o .html si {FORMATO}=html|dual) — Program charter, gate evaluations, resource tracking, dependency control, proposal QA scorecard, status dashboard, lessons learned.
| HTML | {fase}_Program_Governance_{proyecto}_{WIP}.html | Mismo contenido en HTML branded (Design System MetodologIA v5). Self-contained, WCAG AA, responsive. Tipo: Dark-First Executive. Incluye Gantt de programa con gates como milestones, proposal QA scorecard interactivo, y dashboard RAG de fases. |
Diagramas incluidos:
Autor: Javier Montaño | Última actualización: 12 de marzo de 2026