GitHub - harveer10x/earned-vs-burned-skill: A Claude skill for measuring AI delivery value. Replaces tokens, story points & velocity with one honest metric: outcomes earned vs effort burned. · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
harveer10x
earned-vs-burned-skill
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>2 Commits<br>2 Commits
assets
assets
references
references
LICENSE
LICENSE
README.md
README.md
SKILL.md
SKILL.md
View all files
Repository files navigation
Earned vs Burned — Claude Skill
An open source Claude skill for measuring what actually matters in AI-native delivery.
By Harveer Singh | Author, When Data Moves | Founder, Rizz Wireless
The Problem
Every team building with AI is measuring the wrong things.
Token usage. Lines of code. Story points. Velocity. Hours burned. These are burned metrics — they measure effort, not value. A model that hallucinates in 100 tokens is not better than one that solves the problem in 10,000. 500 lines of code that don't ship earn nothing. 40 story points closed on work that never reaches production delivers zero business value.
The only measure that matters: did we earn it?
The Framework
Value is only EARNED when a tangible, verifiable business outcome is achieved. Until that point, all effort is only BURNED .
This is the Earned vs Burned Framework — originally built at Deloitte in 2010 for a Sysco Foods data factory processing 1M+ SKUs (a human-AI hybrid workflow that predated the term). Now generalised for AI-native software delivery.
The Outcome Hierarchy
Level<br>Gate<br>Earned<br>What it means
Not Started<br>0.00<br>Backlog. Zero burn, zero earn.
In Progress<br>0.00<br>Effort accumulating. Still zero earned.
Dev Complete<br>0.25<br>Code written and unit-tested. Partial.
QA Passed<br>0.60<br>Tested and accepted. Meaningful but not in prod.
Deployed to Prod<br>0.85<br>Running in production. Close — but not confirmed.
Outcome Verified<br>1.00<br>KPI moved. User confirmed. Revenue impacted. The only full earn.
The Key Metrics
Metric<br>Formula<br>Target
Earn Rate %<br>L5 outcomes ÷ Total stories<br>70%+
Earned / Hours<br>Total Earned ÷ Total Hours<br>>0.10
Earned per AI Token<br>Total Earned ÷ Total Tokens<br>Trending up
Outcome Verification %<br>L5 verified ÷ L4+L5 deployed<br>Trending up
Earned per AI Token is the metric the industry doesn't have yet. It replaces token volume entirely.
What This Skill Does
Install this skill into Claude and it can:
Pull tasks from any project tool — Linear, Asana, GitHub Issues, Jira, Azure DevOps, or a pasted/CSV list
Score each task against the 5-level Outcome Hierarchy
Calculate all metrics — Earn Rate, E/H Ratio, Earned per Token, Outcome Verification %, Team Effectiveness
Generate an Earned Value Report — one page, three numbers, replaces your velocity report
Coach your team — ends every report with the question that changes delivery culture: what is the verifiable outcome that will confirm this work is done?
Works for FTE teams, outsourced/offshored delivery, AI-agent workflows, or any mix.
Installation
Option 1 — Install the .skill file (Claude Desktop / Cowork)
Download earned-vs-burned.skill from the Releases page
In Claude Desktop or Cowork: Settings → Capabilities → Install Skill
Drop the .skill file in
Option 2 — Manual install (Claude Code)
# Clone the repo<br>git clone https://github.com/[your-org]/earned-vs-burned-skill
# Point Claude at the skill directory<br># Add to your .claude/settings.json:<br># "skillPaths": ["./earned-vs-burned"]
Usage Examples
Once installed, just talk to Claude naturally:
"Score my Linear sprint against the Earned vs Burned framework"
"Here are my Jira tasks — how much value did we actually earn this sprint?"
"We burned 400 hours and 2M tokens this month. What did we earn?"
"I'm an outsourcing vendor — help me prove our value to the client using outcome metrics"
"Pull our GitHub issues and give me an Earned Value Report"
Repository Structure
earned-vs-burned/<br>├── SKILL.md # Core skill...