Skip to content
cccskills
FreePublished on GitHub

codexkit-pmbok8-earned-value

Calculate and interpret Earned Value Management (EVM) metrics per PMBOK 8 Measurement Performance Domain. Compute SPI, CPI, EAC, ETC, TCPI, and generate variance narratives with corrective action recommendations. Use during project execution to assess schedule and cost performance.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md5.0 KB
  • agents/openai.yaml186 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Earned Value Management Analyst

When to Use

  • During project execution when tracking schedule and cost performance
  • At monthly or sprint-end status reporting cycles
  • When stakeholders need objective performance data beyond percentage-complete guesses
  • When forecasting final project cost (EAC) using multiple methods

Procedure

Step 1 — Collect Baseline Data

  1. Confirm Budget at Completion (BAC)
  2. Record Planned Value (PV) at the reporting date
  3. Record Earned Value (EV) — value of work actually completed
  4. Record Actual Cost (AC) — money spent to date

Step 2 — Calculate Core Metrics

MetricFormulaInterpretation
SVEV − PV< 0 = behind schedule
CVEV − AC< 0 = over budget
SPIEV / PV< 1.0 = behind schedule
CPIEV / AC< 1.0 = over budget

Step 3 — Forecast Completion

MethodFormulaWhen to Use
EAC (typical)BAC / CPICurrent CPI trend continues
EAC (atypical)AC + (BAC − EV)Variance was one-time
EAC (SPI×CPI)AC + (BAC − EV) / (CPI × SPI)Both schedule and cost pressure
ETCEAC − ACRemaining spend
TCPI (BAC)(BAC − EV) / (BAC − AC)Efficiency needed to hit BAC
TCPI (EAC)(BAC − EV) / (EAC − AC)Efficiency needed to hit new EAC
VACBAC − EACForecast variance at completion

Step 4 — Generate Narrative

  1. Summarize performance in plain language (ahead/behind, over/under)
  2. Apply traffic-light rating: SPI/CPI ≥ 0.95 = 🟢, 0.8–0.94 = 🟡, < 0.8 = 🔴
  3. Recommend corrective actions for any metric in 🟡 or 🔴 zone
  4. Note trends by comparing with previous period metrics

Inputs

InputRequiredFormat
BAC (total budget)YesCurrency amount
PV (planned value to date)YesCurrency amount
EV (earned value to date)YesCurrency amount
AC (actual cost to date)YesCurrency amount
Prior period SPI/CPIRecommendedDecimal (for trend)

Output

## EVM Status Report — [Project Name] — Period [X]

### Performance Summary

| Metric | Value | Status |
|--------|-------|--------|
| BAC | $500,000 | — |
| PV | $200,000 | — |
| EV | $180,000 | — |
| AC | $210,000 | — |
| SV | -$20,000 | 🟡 Behind schedule |
| CV | -$30,000 | 🔴 Over budget |
| SPI | 0.90 | 🟡 |
| CPI | 0.86 | 🔴 |

### Forecast

| Method | EAC | VAC |
|--------|-----|-----|
| Typical (CPI trend) | $581,395 | -$81,395 |
| Atypical (one-time) | $530,000 | -$30,000 |
| SPI×CPI compound | $612,745 | -$112,745 |

### TCPI
- To hit BAC: **1.10** (achievable with corrective action)
- To hit EAC: **0.86** (current pace)

### Corrective Actions
1. CPI 🔴: Review scope for non-essential deliverables to reduce remaining cost
2. SPI 🟡: Fast-track critical path activities in next 2 sprints
3. Escalate to sponsor if CPI does not improve to 0.95 by Period X+2

Definition of Done

  • All 7 EVM metrics calculated correctly
  • At least 2 EAC methods presented
  • Traffic-light status applied to SPI and CPI
  • Corrective actions provided for any metric in 🟡 or 🔴
  • Narrative is in plain language (not just formulas)

Examples

Prompt

My project has BAC = $500,000. As of end of Month 4:
PV = $200,000, EV = $180,000, AC = $210,000.
Last month SPI was 0.93, CPI was 0.89.
Generate a full EVM report with forecasts and corrective actions.

Quality Criteria

  • Data sources and assumptions are explicitly stated
  • Calculations are reproducible from provided inputs
  • Visualizations or tables have clear labels, units, and time ranges
  • Caveats and confidence levels are documented for estimates

Verification (4C)

CheckQuestion
CorrectnessAre formulas, aggregations, and statistical methods applied correctly?
CompletenessDoes the analysis cover all requested metrics and time ranges?
Context-fitAre the chosen metrics relevant to the business question being answered?
ConsequenceIf this data were used for a decision today, what blind spots remain?

Edge Cases

  • Missing or incomplete data — Document gaps and their potential impact on conclusions. Provide ranges instead of point estimates.
  • Outliers skewing results — Report with and without outliers. Document the decision to include or exclude.
  • Changing data definitions mid-period — Split analysis at the change boundary and note the schema difference.

Changelog

  • v1.0.0 — Initial release

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

See all skills by hoavdc

Report a problem with this skill