Skip to content

cynco-labs/ai-accounting-skills / accounting-engagement/skills/revenue-recognition

revenue-recognition

Verified

Revenue recognition analysis under MPERS/MFRS for material money in. Use when revenue recognition, sales cut-off, deferred revenue, principal vs agent.

FileKindSize
SKILL.mdskill md1.2 KB
---
name: revenue-recognition
description: Revenue recognition analysis under MPERS/MFRS for material money in. Use when revenue recognition, sales cut-off, deferred revenue, principal vs agent.
disable-model-invocation: true
---
# /revenue-recognition

## Purpose

Thin alias into **classify** — revenue theme only.  
Same doctrine: `shared/classify-substance.md`.  
Same output folder: `workpapers/analysis/revenue_recognition.md`.

## Steps

1. Ensure `workpapers/transactions.json` exists (run **extract** if not).  
2. Set `classify_depth` = `standards_aware` for this theme.  
3. Load `references/jurisdictions/malaysia/standards/revenue_recognition.md` (or active jurisdiction pack).  
4. Follow **classify-transactions** steps 1–3 focused on material credits / sales streams.  
5. Write `workpapers/analysis/revenue_recognition.md` from `references/schemas/analysis_pack.example.md`.  
6. Apply concluded COA codes; update `payee_map.json`; re-run classify script for affected lines.

**Done when:** revenue pack on disk with sources, standard ref, conclusion → codes; open items listed.

## Do not

- Invent a second pipeline  
- Code all bank credits as sales without substance  
- Skip structured asks when recognition date is ambiguous  
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall