FinOps — Cloud Financial Operations

graph TD
    subgraph Core["FinOps Core"]
        A[metodologia-finops]
        A1[S1: Maturity Assessment]
        A2[S2: Cost Visibility]
        A3[S3: Waste Identification]
        A4[S4: Optimization]
        A5[S5: Unit Economics]
        A6[S6: Rate Optimization]
        A7[S7: Governance]
        A8[S8: Operating Model]
    end
    subgraph Inputs["Inputs"]
        I1[IaC / Terraform / CloudFormation]
        I2[Billing Exports / Cost Explorer]
        I3[Architecture Diagrams]
        I4[Tagging Strategy Docs]
    end
    subgraph Outputs["Outputs"]
        O1[FinOps Assessment Report]
        O2[Quick Wins Summary]
        O3[Optimization Roadmap]
    end
    subgraph Related["Related Skills"]
        R1[metodologia-technical-feasibility]
        R2[metodologia-cost-estimation]
        R3[metodologia-software-viability]
        R4[metodologia-sector-intelligence]
    end
    I1 --> A
    I2 --> A
    I3 --> A
    I4 --> A
    A --> A1 --> A2 --> A3 --> A4
    A4 --> A5 --> A6 --> A7 --> A8
    A --> O1
    A --> O2
    A --> O3
    A --- R1
    A --- R2
    A --- R3
    R4 --> A

# FinOps Assessment — {proyecto}
## Resumen Ejecutivo
> Hallazgo clave en 3 lineas.
## S1: Evaluacion de Madurez FinOps
| Dominio | Score (1-5) | Evidencia | Recomendacion |
|---------|-------------|-----------|---------------|
## S2-S8: [secciones completas]
## Roadmap de Optimizacion
```mermaid
gantt
    title Roadmap FinOps
    section Quick Wins
    ...

**Formato XLSX (para audiencia financiera):**

**Formato HTML (bajo demanda):**
- Filename: `FinOps_Assessment_{project}_{WIP}.html`
- Estructura: HTML self-contained branded (Design System MetodologIA v5). Light-First Technical page con maturity radar chart, waste breakdown interactivo, y optimization roadmap con filtros por tier. WCAG AA, responsive, print-ready.

**Formato DOCX (bajo demanda):**
- Filename: `FinOps_Assessment_{project}_{WIP}.docx`
- Generado con python-docx bajo Metodología Design System v5: portada, TOC automático, encabezados/pies de página con marca, tablas zebra, tipografía Poppins (headings navy), Montserrat (body), acentos dorados

**Formato PPTX (bajo demanda):**
- Filename: `{fase}_{entregable}_{cliente}_{WIP}.pptx`
- Generado via python-pptx con MetodologIA Design System v5. Slide master con gradiente navy, títulos Poppins, cuerpo Montserrat, acentos dorados. Máx 20 slides ejecutivo / 30 técnico. Notas del orador con referencias de evidencia. Secciones: FinOps Maturity Assessment, Cost Visibility & Waste Identification, Top Optimization Opportunities (Quick Wins / Medium / Strategic), Unit Economics, Governance & Operating Model, Roadmap de Implementación.

## Evaluacion

| Dimension | Peso | Criterio | Umbral Minimo |
|-----------|------|----------|---------------|
| Trigger Accuracy | 10% | El skill se activa correctamente ante prompts de FinOps, cloud cost, rightsizing | 7/10 |
| Completeness | 25% | Las 8 secciones estan pobladas con contenido basado en evidencia; unit economics definidos | 7/10 |
| Clarity | 20% | Ejecutivos no tecnicos pueden entender el resumen; costos expresados en magnitudes con contexto | 7/10 |
| Robustness | 20% | Edge cases cubiertos (multi-cloud, serverless, no billing data); workarounds documentados | 7/10 |
| Efficiency | 10% | El modo operacional correcto se selecciona segun contexto; no se genera analisis innecesario | 7/10 |
| Value Density | 15% | Cada optimizacion tiene ahorro estimado (%), esfuerzo, y timeline; zero recomendaciones genericas | 7/10 |

**Umbral minimo global: 7/10.** Si alguna dimension cae por debajo, el entregable requiere revision antes de entrega.

## Cross-Section Traceability

- S1 Maturity → S8 Operating Model (maturity gaps drive practice design)
- S2 Visibility → S3 Waste (visibility enables waste identification)
- S3 Waste → S4 Optimization (waste categories map to optimization actions)
- S4 Optimization → S5 Unit Economics (optimizations improve unit economics)
- S5 Unit Economics → S7 Governance (unit economics define budget thresholds)
- S6 Rate Optimization → S4 Optimization (rate optimization is a subset)
- S7 Governance → S8 Operating Model (governance requires organizational support)

## Escalation to Human

- Cloud spend at enterprise scale (enterprise-grade negotiation needed)
- Multi-cloud with no centralized visibility (requires FinOps platform selection)
- Engineering teams resistant to cost accountability (organizational change needed)
- Compliance constraints that conflict with optimization (legal review needed)
- Contract renegotiation opportunity (commercial/legal expertise)

## Execution Workflow

1. **Data Collection (1-2 hours):** Gather billing exports, IaC, architecture docs, tagging info
2. **Maturity & Visibility (2-3 hours):** Score maturity, map cost allocation, identify gaps
3. **Analysis (3-5 hours):** Waste identification, optimization opportunities, rate analysis, unit economics
4. **Strategy (2-3 hours):** Governance model, operating model, implementation roadmap

**Typical engagement:** 3-5 days for organizations with moderate cloud spend.

## Output Configuration

- **Language**: Spanish (Latin American, business register — simple, clear, concise, direct)
- **Attribution**: Expert committee of the MetodologIA Discovery Framework
- **Tagline**: *"Construido por profesionales, potenciado por la red agéntica de MetodologIA."*

## Output Artifact

**Primary:** `FinOps_Assessment_{project}.md` (or `.html` if `{FORMATO}=html|dual`) — Full 8-section FinOps assessment with cost breakdowns, optimization roadmap, and governance model.

**Secondary:** `FinOps_QuickWins_{project}.md` — Executive summary (S3 waste + S4 quick wins + estimated savings).

**Diagrams included:**
- Quadrant chart: optimization opportunities (savings potential x implementation effort)
- Mindmap: cost allocation taxonomy
- Gantt chart: optimization implementation timeline

## Validation Gate

- [ ] All 8 sections populated with evidence-based content
- [ ] Cost figures expressed in magnitudes, NEVER exact prices
- [ ] Every optimization opportunity has estimated savings % and effort level
- [ ] Unit economics defined with business-relevant metrics
- [ ] Governance model is actionable (not just "tag resources")
- [ ] FinOps maturity scored with observable evidence
- [ ] Cross-section traceability complete

## Output Format Protocol

| 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. |
| `xlsx` | On demand | Cost breakdown sheets (recommended for finance audience). |

## Operational Modes

| Mode | Focus | Best For |
|---|---|---|
| `assessment` (default) | Full 8-section analysis | Annual review, Phase 1/4 input |
| `optimization` | S3 + S4 + S6 deep, ROI-focused | Known waste, need quick savings |
| `framework` | S1 + S7 + S8 deep, practice design | Greenfield FinOps implementation |

## Additional Resources

### References (Progressive Disclosure — Level 3)
- `Read ${CLAUDE_SKILL_DIR}/references/knowledge-graph.mmd` — Domain knowledge graph
- `Read ${CLAUDE_SKILL_DIR}/references/body-of-knowledge.md` — Academic and industry sources
- `Read ${CLAUDE_SKILL_DIR}/references/state-of-the-art.md` — Trends 2024-2026

### Examples
- `Read ${CLAUDE_SKILL_DIR}/examples/sample-output.md` — Golden reference output
- `Read ${CLAUDE_SKILL_DIR}/examples/sample-output.html` — Branded HTML
- `Read ${CLAUDE_SKILL_DIR}/examples/sample-output.xlsx-spec.md` — Excel spec for cost data

### Prompts
- `Read ${CLAUDE_SKILL_DIR}/prompts/use-case-prompts.md` — Ready-to-use prompts
- `Read ${CLAUDE_SKILL_DIR}/prompts/metaprompts.md` — Meta-strategies

---