Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.
npx skills add https://github.com/cbrock84/headcount --skill revenue-recognition
Cash received is not revenue earned. The gap between them is where deals get restructured after
signature and where quarters get restated.
**This structures the question and tells you what to ask. Revenue recognition is a technical
accounting matter under standards such as ASC 606 and IFRS 15 — conclusions on a material or unusual
contract need your auditors or a qualified accountant, not a checklist.**
Recognition follows the transfer of control to the customer, worked through in five steps: identify
the contract, identify the distinct performance obligations, determine the transaction price,
allocate it across the obligations, then recognize as each is satisfied.
Most disputes happen at step two and step four. What sales sold as one thing is frequently several
obligations for accounting purposes — software plus implementation plus support — and the price has
to be allocated across them on standalone selling price, not on how the quote was written.
These belong in a pre-signature review, because after signature the only remedy is an amendment the
customer has no reason to agree to:
purposes, however long the stated term is.
will be no significant reversal.
performance obligation carved out of today's price.
single most common cause of restatement, and by construction finance does not know they exist.
Recognition treatment is a deal input, not a post-signature discovery. A concession that costs
nothing commercially can move revenue across a period boundary, and by the time finance sees the
signed paper the trade has already been made.
Give revenue:chief-revenue-officer and revenue:pricing-and-packaging a small set of standard
structures that recognize cleanly, and route anything outside them through review before signature —
alongside legal-risk:contract-review, which owns the legal exposure the same clauses create.
The deferred balance is work owed, not money banked. Track it by cohort and obligation so you can
answer what it is composed of and when it releases. A balance nobody can decompose is one that
surprises you.
Take cbrock84/revenue-recognition from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.