본문으로 건너뛰기
cccskills
무료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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

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

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hoavdc/CodexKit252026년 10월 11일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hoavdc/CodexKit252026년 10월 11일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hoavdc/CodexKit252026년 10월 11일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hoavdc/CodexKit252026년 10월 11일 업데이트

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

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hoavdc/CodexKit252026년 10월 11일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

hoavdc/CodexKit252026년 10월 11일 업데이트

hoavdc의 스킬 모두 보기

이 스킬의 문제 신고