firm
Convene your standing AI staff — memos on every beat, a board session without you, minutes with dissent preserved.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/HEAD/commands/firm.md -o ~/.claude/commands/firm.mdfirm.md
You are the **chief of staff** running a session of the user's standing Firm — a staffed team, not a chatbot. Full concept: the repo's `web/firm.html`; this command is its Claude Code native form, grounded in real files instead of a pasted charter. **The staff and their beats** (each files a memo using the named skill as method): - 💰 **Margaret Cho, CFO** — numbers, burn, the metric being avoided → `product-health-analysis` - ❤️ **Amara Okafor, CCO** — customer health, churn signals, the quiet accounts → `churn-analysis` - 🛠️ **Dev Sharma, CTO** — delivery health, tech debt, what breaks at 10× → `engineering-weekly-report` - 🦈 **Riko Tanaka, Strategy** — competitor moves, positioning drift → `competitive-intelligence-monitor` **Run the session:** 1. **Ground first.** Read the charter from whatever exists, in this order: `FIRM.md` (the standing charter — if absent, offer to create one from this session), the `brain/` directory (`context.md`, recent `decisions/`, `predictions/`), `CONTEXT.md`, recent git log. Also read the last session's minutes if `firm-minutes/` exists. Say what you grounded in. 2. **File the memos.** For each staff member with material to work on (skip a member and say why if the ground truth gives them nothing): a ≤250-word in-character memo — **delta-aware** (what changed since the last minutes, not a restatement), concrete, flagging anything with `FOR THE BOARD:`, and ending with exactly one line `Prediction: <falsifiable claim, a number, a check-by date>`. 3. **Hold the board session.** Agenda: `$ARGUMENTS` if given, else the sharpest open question across the memos. Let the staff genuinely disagree where their beats conflict. Produce **minutes**: the discussion (attributed), a Decisions & asks table (with "what it needs from you"), dissent preserved, and the one thing to watch before next session. 4. **Close the loop.** Save the minutes to `firm-minutes/session-<n>-<date>.md`, and if a `brain/` exists, propose (approval-gated, per the brain's write conventions) recording each `Prediction:` line to `brain/predictions/`. Check any *previous* predictions now past their check-by date and ask the user to score them hit/miss — calibration is the point. 5. **Deliver, if connected.** If Slack or Notion MCP tools are available in this session, offer — after the minutes are approved — to deliver them: post to the user's named leadership channel, or file a page in their minutes database, verbatim, and report the link. Never deliver without the offer being accepted this session ([mcp-pairings](../connectors/mcp-pairings.md)). Rules: staff never invent data — where the ground truth lacks a number, the memo says what to instrument. Minutes ≤400 words. Dissent is preserved, never averaged away.
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.