coreyhaines31/makerskills / skills/company-brain
company-brain
VerifiedYour team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain — personal notes go there, not here. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 19.3 KB |
| references/auto-sync-sources.md | markdown | 4.7 KB |
| references/rollout.md | markdown | 1.9 KB |
| references/schema.md | markdown | 8.2 KB |
| references/vault-config.md | markdown | 4.0 KB |
references/rollout.md
View on GitHub# Rolling out a company brain
Adoption beats announcement. Launching to the whole company on day one creates a pile of unreviewed captures you spend months culling, and people stop trusting answers before the brain has earned any trust.
## Phase 1 — Pilot (2–4 weeks)
- **One workflow**, seeded per "Start narrow" in `vault-config.md`.
- **One or two people** who live in that workflow daily and will actually run `/cb review`.
- Capture everything relevant to the workflow; don't capture outside it yet.
- Hold a weekly review pass. If it slips, fix that before anything else; it's the habit everything else depends on.
## Phase 2 — Prove value
Move on only when all three are true:
| Signal | Bar |
|---|---|
| Queries answered | The pilot group asks it real questions weekly and gets useful answers |
| Review cadence | Weekly review has held for 3+ weeks; the unreviewed queue isn't growing |
| Trust | Answers cite `verified` sources often enough that people stop double-checking |
If a signal misses, narrow rather than widen: fewer dirs, fewer sources, a tighter workflow.
## Phase 3 — Expand
- Add **one** workflow (and its dirs) at a time, with an owner who runs review for it.
- Add people in the order they'll contribute, not by org chart.
- Turn on auto-sync (call transcripts, Slack, CRM) per workflow only after manual capture has proven which content is worth keeping. Auto-sync on day one multiplies the review queue before anyone knows what good looks like.
- Set sensitivity levels before leadership or confidential content arrives, not after.
## Anti-patterns
- **The big launch.** All dirs, all people, all syncs at once. Review can't keep up, so trust never forms.
- **Capture without review.** A growing `unreviewed` queue is the leading indicator of a brain nobody trusts.
- **Measuring pages, not answers.** Page count is vanity. Questions answered without asking a person is the metric.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |