Five people, five CLAUDE.md files, no owner.
That is the normal state of a team using agents. Everyone tuned their own file, nobody measures it, and the rules that matter — post, email, price, refund, deploy — are different in each folder. This installs one library everyone uses, with gates that actually run.
- ≤25
- people
- 10 business days
- EN or 中文
What gets installed
- One rules file, owned.
A single CLAUDE.md plus an AGENTS.md pointer, with one named owner and a review date. No per-repo forks.
- A role library.
Lead, researcher, builder, checker, writer — each with a brief, an owned path and a definition of done.
- Seven approval gates.
Post, customer email, price change, refund, listing, payment, deploy. Each with the exact rule and who may pass it.
- A validated skill set.
The skills your team already uses, checked for description matching, parse errors and test coverage before they are shared org-wide.
- A measurement sheet.
Tasks shipped, rework rate and tokens per task, one row per week, so the file stops drifting.
- A handover recording.
Sixty minutes, recorded, so the next person can maintain it without you.
What I need from you
- Read access to the context files.CLAUDE.md, AGENTS.md and the skill folders. No keys, no production data.
- One 30-minute call.Tools in use, team size, and the three actions you never want an agent to take alone.
- A named owner.One person who will keep the file current after handover.
No access to customer data, payment credentials or production systems is requested. Files are deleted 30 days after delivery.
Price and terms
$990 for the first three teams; $1,990 after that. Ten business days from the moment the files and the call are done. Invoice in USD, purchase order fine, payment by card or bank transfer.
If the delivered library misses the written scope, full refund. One revision round included.