What a piece is
Four kinds of things, all files you own.
Everything in the box is a plain file that installs into Claude Code, Anthropic's system environment. Nothing is hosted, nothing is rented, and every piece arrives with its own instruction document.
- Agents. Plain-text .md files, each a one-page job description for an advisor: what it watches for, what it argues for, when it speaks up.
- Skills. Plain-text .md instruction sets you invoke by name, so a repeated judgment call runs the same way every time.
- Architectures. The file structures and maps underneath: memory, knowledge graphs, routing, doctrine, and six small always-on programs (hooks) that enforce the rules a model cannot be trusted to remember.
- Guides. Documents you read: the teaching curriculum paying clients received, the install quick-start, and a prompt pack for fitting every piece to your own firm.
Agents · 24 seats
Who staffs the firm?
Twenty-four advisor seats, organized into working teams. Each seat is one .md file with one job.
- The advisory board, 6 seats. Strategy, finance, counsel, power, product, and a standing contrarian built to argue against the plan on purpose.
- The go-to-market team, 4 seats. Offer design, pricing, market research, and page design, run before anything goes on sale.
- The systems team, 3 seats. An architect who reviews before anything gets built, an engineer who fixes, an auditor who checks claims against what is actually true.
- The bid-review team, 3 seats. A fact verifier, an evaluator panel that scores your draft the way a buyer's panel would, and a package checker for the final upload.
- The legal-review team, 3 seats. A guardian with a standing protection checklist, an adversary that reads your agreement the way the other side's counsel will, and a fairness pass.
- The key-account team, 3 seats. The pattern for managing one important relationship: a context keeper, a communications writer, an opportunities advisor.
- Two standing specialists. A meeting coach that reads call transcripts moment by moment, and a security auditor that sweeps for exposed keys and unsafe files.
Skills · 28
What does it actually do, day to day?
Twenty-eight working skills, each invoked by name, each with its own instruction document. The complimentary manual walks every one of them; here they are by the work they do.
- Run the day, 5. The chief of staff (your priorities and decision queue), the executive assistant charter, the daily dump that files a raw update, the session close-out that moves what matters into memory, and the usage check that asks whether you are even using the system the right way.
- Write, 7. Notes in your own voice to a specific person, long-form co-writing, the clarity pass that turns dense prose into plain sentences, the house voice for published work, research-to-email conversion, turning a client session into a finished package, and the keeper of your site's house style.
- Sell and bid, 7. The marketing and product department, the offer-to-buyer path, proposal voice (the register a real proposal is written in), bid and RFP response, grant writing, margin protection before you sign, and the manager for one specific important relationship.
- Check, 4. The pre-publication quality check, the bid-review panel, the agreement review, and the pattern finder that turns a pile of one-off observations into a rule.
- Run the machine, 5. The strategy board convener, model cost routing that picks the cheapest Claude that can do the job, the self-documenter that maps the whole setup, environment configuration, and the daily intake router.
Architecture
What holds it all together?
The structures underneath the staff: what the firm knows, how it routes, and the rules that hold no matter what.
- The memory schema. Four kinds of note and one index, read automatically at the start of every session, so a mistake corrected once never has to be corrected twice.
- The knowledge-graph method. One-page maps per subject that survive a long conversation the way a long document cannot. Written on placeholder companies; no client data ships inside it.
- The routing tables. The maps naming which file owns which kind of information, loaded before you say a word, so nothing gets filed twice or nowhere.
- The doctrine pack. Ten starting rules, written to be replaced by the rules your own firm learns.
- Six always-on hooks. Small programs, not model judgment: a fast check on every save, a slow check on request, and the voice and claim rules enforced mechanically.
- The session lifecycle. Short sessions, closed by a real ritual, restarted clean, so the system compounds instead of drifting.
Install
How does it get installed?
Plug and play, four steps, one business day.
- 1. Answer three questions. What kind of firm you are, what tools run your work today, and who you serve most. Your answers shape the assembly.
- 2. Get Claude Code. Anthropic's environment, from about $20 a month, paid to Anthropic. The install guide walks you into it if you have never opened it.
- 3. Copy the folders in. The box arrives by email within one business day of your order. Each piece sits beside its own instruction document.
- 4. Fit it to your firm. The prompt pack customizes each piece to your context: your services, your buyers, your voice. Support is megan@rbdco.ai, answered the same business day.
