agentleFS
pradeep-sankaran-07pradeep-sankaran-07/team-os-gdrive-template/.claude/skills/solution-brief/SKILL.md

solution-brief

Skill0 starsChanged 2 months agoMITView on GitHub

Create the Solution Brief: the decision document a prospect uses to decide whether to buy, with the business case behind it. Use after discovery, when a prospect needs something to evaluate and circulate internally. Triggers: "write a brief for <company>", "create a solution brief", "draft the decision document", "build the business case for <company>". BOUNDARY: this is the DECISION DOCUMENT and the BUSINESS CASE, the argument for buying. A priced list of what they get is a different document. A deal often needs both, produced separately. NOT for public marketing content (use acme-marketing) and NOT for an existing customer's review (use account-review).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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. Distinctive:

    Read the account folder, especially the discovery calls, and the three context files above.

    line 29
  2. Distinctive:

    Do not hedge across three angles.

    line 39
  3. Very specific:

    Write to output_location. Append one line to _ops/log.md.

    line 61
  4. Distinctive:

    Every number has its assumption written next to it.

    line 67
  5. Distinctive:

    Every claim about the prospect traces to a named call or document.

    line 68
  6. Distinctive:

    No em dashes. A human has read it end to end.

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Solution brief

Step 1 - Gather

Read the account folder, especially the discovery calls, and the three context files above. Note the prospect's own words for their problem: the brief uses their vocabulary, not ours.

Step 2 - Choose the dominant value angle

This is the step that decides whether the brief works. See references/value-angles.md. Pick exactly one angle and build the whole document around it.

Do not hedge across three angles. A brief that argues everything argues nothing, and the person who has to circulate it internally cannot summarise it in a sentence. If two angles look equally strong, that means discovery is incomplete; say so and ask, rather than including both.

A human confirms the angle before you draft. This is the judgment the skill does not make.

Step 3 - Draft

  1. The problem, in their words - quoted or closely paraphrased from discovery, with the call it came from named.
  2. What changes - what their operation looks like afterwards. Concrete, not adjectival.
  3. The case - the numbers, each one traceable to an assumption stated on the page. An unsourced number in a decision document is worse than no number.
  4. How it lands - what implementation actually involves, including what it asks of them. Understating this is how a deal closes and an onboarding fails.
  5. What we need from you - the decision being asked for, and by when.

Step 4 - Record

Write to output_location. Append one line to _ops/log.md. Note the chosen angle in accounts/<slug>/summary.md, so the next person does not rediscover it.

Review before delivering (required)

  • One angle, carried all the way through.
  • Every number has its assumption written next to it.
  • Every claim about the prospect traces to a named call or document.
  • Nothing in it that we would not say out loud to them.
  • No em dashes. A human has read it end to end.

Things that have gone wrong before

  • Lead with one angle, not three. Why: a brief covering every possible benefit reads as a brochure and gets skimmed. The champion needs one sentence they can repeat to their own boss. (2026-09-16)

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.