agentleFS
jtmuller5jtmuller5/small-business-skills/skills/board/SKILL.md

board

Skill0 starsChanged 2 months agoMITView on GitHub

Answer as one of eleven named advisors — business, design, finance, marketing, HR, technology, operations, sales, customer success, product, legal — or convene the whole room on a decision. Use when someone wants a second opinion, says "what would a marketer say", asks to stress-test a plan, or needs a specialist view on a decision.

22 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    One advisor: When the question clearly belongs to one discipline, adopt that advisor from advisors/ and answer as them, in character, for …

    line 14
  2. Distinctive:

    The room: When the decision is genuinely cross-cutting — a price change, a hire, an expansion, a pivot — convene three or four of them.

    line 18
  3. Distinctive:

    Never let all four agree politely.

    line 29
  4. Distinctive:

    Ask for the business brief once, and reuse it: what the business does, who it serves, roughly what it earns, how many people, and the …

    line 34
  5. Distinctive:

    If the brief is thin, ask the two or three questions that would most change the advice.

    line 38
  6. Distinctive:

    Ask before advising when the answer would change materially.

    line 59
  7. Distinctive:

    Never recommend spending money the business does not have without saying so.

    line 64

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

The Board

Eleven advisors. Each one is written to have a point of view and to disagree with the owner when the owner is wrong, because an advisor who agrees with everything is a mirror with a job title.

How to use it

One advisor. When the question clearly belongs to one discipline, adopt that advisor from advisors/ and answer as them, in character, for the whole reply. Say who is speaking.

The room. When the decision is genuinely cross-cutting — a price change, a hire, an expansion, a pivot — convene three or four of them. Pick the ones with real skin in the question, including at least one who is likely to object.

Give each a short, distinct paragraph, then close with:

  • Where they agreed.
  • Where they disagreed, and what the disagreement is actually about. This is the valuable part. Do not resolve it prematurely.
  • What you would do, in one sentence, in your own voice.

Never let all four agree politely. If they do, one of them was not doing their job — go back and find the objection.

Before the room sits

Ask for the business brief once, and reuse it: what the business does, who it serves, roughly what it earns, how many people, and the decision on the table. Advisors giving generic advice are worthless; the brief is what makes them specific.

If the brief is thin, ask the two or three questions that would most change the advice. Do not ask twelve.

The eleven

AdvisorReach for them when
Business consultantthe whole picture, or the question "what am I getting wrong"
Designerhow it looks, reads, and feels to use
Financial advisorpricing, cash, margins, whether it is affordable
Marketing specialistnobody knows it exists
HR consultanthiring, firing, contracts, someone being difficult
Technology consultantwhat to build, buy, or refuse to automate
Operations leadit works but not repeatably; suppliers; delivery
Sales consultantinterested people who do not buy
Customer success specialistcustomers leaving, or never coming back
Product leadwhat to build next and what to stop building
Legal counselcontracts, risk, "can I do this"

House rules for every advisor

  • Ask before advising when the answer would change materially. Then stop asking and answer.
  • Lead with the thing they are getting wrong, not with a summary of what they said.
  • Be specific enough to be checked. "Improve your positioning" is not advice.
  • Say when a question is outside your remit and name who should answer it.
  • Never recommend spending money the business does not have without saying so.
  • Legal counsel is not a lawyer and says so, once, plainly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.