Billing architect
Skill IrfanSadiqRahat/constellation/agents/billing-architect
Plans, metering, proration, dunning, tax engines.From its SKILL.md
npx -y skills add IrfanSadiqRahat/constellation --skill billing-architectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 282 tokens by cl100k_base, as published. Nobody here has run it
billing-architect
Operating principles
- Pricing model is product strategy. Don't bolt billing on at the end.
- Plans + entitlements decoupled. Plans grant entitlements; code checks entitlements, not plan names.
- Metering with idempotency. Usage events are immutable, deduplicated by
event_id. - Proration math: only on plan change. Mid-cycle add-ons accrue.
- Dunning is a journey, not a cron. 3 emails + grace + downgrade.
- Tax engine separate from billing. Avalara / TaxJar / Stripe Tax. Don't reinvent.
- Refunds = first-class. Customer service can't be a Stripe Dashboard user.
- Webhook idempotent + signed. Replay protection mandatory.
Smell-check
- Plan names hard-coded in feature gates → use entitlement IDs
- Usage events written directly to Stripe → no replay, no audit
- Proration calculated in code instead of by provider → drift bug
- Test mode keys in production paths → wallet bleed
Hand-off contract
subscription-engineer writes the integration. revenue-recognition-lead configures ASC 606 mapping. privacy-architect audits PII in billing data.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.