菜单
Use when specifying SaaS usage events, billing, credits, refunds, dunning, finance handoff, and testable metering controls; use pricing-and-packaging for commercial tier design.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when defining a game's player promise, product hypotheses, platform options, production model, vertical-slice evidence, commercial boundaries, or greenlight decision before detailed requirements.
Use when specifying testable game software requirements for player experience, gameplay state, platforms, multiplayer, saves, content, performance, accessibility, telemetry, security, builds, release, or live operations.
Use when designing game client, authoritative state, engine integration, content, saves, multiplayer backend, platform adapters, telemetry, security, build, and live-operations architecture from an approved game SRS.
Use when turning approved game requirements and architecture into implementable Unity, Godot, Unreal, Apple-native, multiplayer, content-pipeline, build, and telemetry work packages with code and asset contracts.
Use when planning game QA, playtesting, balance, deterministic simulation, save migration, multiplayer network conditions, device performance, accessibility, localisation, security, certification, and release-candidate evidence.
Use when documenting reproducible game builds, signing, artifact promotion, distribution, staged rollout, rollback, crash diagnosis, matchmaking operations, live events, remote config, economy controls, support, or incidents.
| name | 13-saas-billing-and-metering-spec |
| description | Use when specifying SaaS usage events, billing, credits, refunds, dunning, finance handoff, and testable metering controls; use pricing-and-packaging for commercial tier design. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
SaaS billing and metering specification is the next lifecycle deliverable.pricing-and-packaging when that neighbouring route owns the decision or deliverable.| Artefact | Source or provider | Required? | Behaviour when missing |
|---|---|---|---|
| Approved pricing, entitlement, finance, and tenant context | Product owner and finance doctrine | Yes | Stop the affected step, name the missing source, and return only a qualified gap record. |
SaaS billing and metering specification.| Artefact | Consumer | Acceptance condition |
|---|---|---|
| SaaS billing and metering specification | Architecture, finance, API, and test owners | Required sections are populated, source links resolve, and every material requirement or decision has an observable review or test oracle. |
| Evidence | Reviewer | Acceptance condition |
|---|---|---|
Source, decision, trace, and validation record for SaaS billing and metering specification | Requirements quality reviewer | Inputs used, decisions made, checks run, failures, and unassessed items are explicit. |
Read and search are required. Editing is allowed only when the request authorises creation or repair of the named requirements artefact. Publishing, production mutation, destructive action, spending, and certification require explicit authority.
Fallback: if a required file, reviewer, standard source, network check, renderer, or execution capability is unavailable, return the narrowest useful qualified result and mark the affected check not assessed; never convert an unassessed check into a pass.
| Choice or condition | Action | Failure or risk avoided |
|---|---|---|
| A chargeable event cannot be tied to tenant, source, quantity, and idempotency key | Reject the event contract and close the lineage gap. | Unbillable usage, duplicate charges, or unauditable revenue. |
| Required inputs and test oracles are complete | Continue through the existing workflow and record evidence. | A deliverable whose acceptance cannot be reproduced. |
| A mandatory source or owner is missing | Stop the affected branch and issue a qualified gap record. | Fabricated context or unauthorised decisions. |
SaaS billing and metering specification and its acceptance checks.SaaS billing and metering specification from assumed context. Fix: cite the project source or mark the scope blocked.pricing-and-packaging without routing the decision. Fix: hand off the named input and preserve trace links.not assessed and state the release consequence.Generates the requirements specification for the SaaS billing-and-metering pipeline. Sourced from Mersch (financial-metrics rigor) and Golding (control-plane responsibilities).
For every billable or quota-limited action, produce a row:
| Event name | Schema | Granularity | Source service | Sink | Retention raw / aggregate | Used for | Tenant fields |
|---|---|---|---|---|---|---|---|
api.request.completed | {tenant_id, endpoint, ts, status, bytes_in, bytes_out, duration_ms} | per request | Gateway | metering bus | 13 mo / 7 y | rate limit + per-call pricing + analytics | tenant_id, tier |
storage.snapshot | {tenant_id, bytes_used, ts} | hourly | Storage service | metering bus | 13 mo / 7 y | GB-hour pricing | tenant_id, tier |
seat.assigned | {tenant_id, user_id, ts, role} | per change | Identity | metering bus | 13 mo / 7 y | per-seat pricing | tenant_id |
feature.used | {tenant_id, feature_id, ts} | per use | App services | metering bus | 13 mo / 7 y | tier enforcement + analytics | tenant_id, tier |
Every event MUST include tenant_id. Every billable event MUST also include tier, region, and source trace_id. Events missing tenant_id MUST be rejected at the bus ingress and logged.
Document for each price-list line: revenue-recognition pattern (ratable / point-in-time / milestone / usage).
Billing_And_Metering_Spec.md with sections: 1) Metered Event Catalogue, 2) Tenant Context Rules, 3) Transport / Retention / Ordering, 4) Aggregation & Pricing Engine, 5) Revenue Recognition (ASC 606 / IFRS 15), 6) Dunning / Refunds / Credits, 7) Audit & Reconciliation, 8) ERP Handoff, 9) Traceability to PRD pricing and SRS NFRs.
logic.prompt, README.md, references/saas-billing-and-metering-srs-template.md, references/saas-revenue-recognition-spec-template.md.