agentleFS
Sign inStart free
ayleeaylee/agent-os/.claude/skills/brief/SKILL.md

brief

Skill0 starsChanged 4 months agoMITView on GitHub

Write or revise a concise project brief or one-pager. Use when the user asks for stakeholder alignment, a proposal, a one-page brief, or an edit to an existing brief artifact.

80 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, strategy and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 6 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 4 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 5 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 7 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 73 edited versions we read keep these.

  • 3

    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:

    Keep execution state in the linked WORKSTREAM.md.

    line 16
  2. Distinctive:

    After writing, summarize what changed, unresolved questions, and the artifact path.

    line 17
  3. Distinctive:

    If the work changes current execution state, update the linked workstream separately and create a receipt only for that workstream revision …

    line 19
  4. Distinctive:

    Do not invent links, metrics, quotations, or stakeholder positions.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 73 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
<!-- Generated from .agents/skills/brief/SKILL.md; source-sha256: 80d5580c324111d60e98651acf2dcda6b6e9acc5a7815f0a44b21da8ad65443c. -->

Brief

Produce a decision-ready brief, not a transcript of the work that led to it.

  1. Resolve the owner binder. Read its BINDER.md, linked active workstream, relevant area context, and library/reference/me.md when voice matters.
  2. Inspect library/templates/brief.md. Reuse its structure only where each section earns its place.
  3. Establish audience, decision or outcome, evidence, constraints, scope, risks, and next step. Ask only for material facts that cannot be discovered.
  4. For an existing file, preserve settled facts and edit in place. For a new file, write it inside the owner binder with a descriptive filename.
  5. Keep execution state in the linked WORKSTREAM.md; do not duplicate status logs in the brief.
  6. After writing, summarize what changed, unresolved questions, and the artifact path. Do not create a receipt for the document edit.

If the work changes current execution state, update the linked workstream separately and create a receipt only for that workstream revision transition.

Do not invent links, metrics, quotations, or stakeholder positions. Do not commit or publish unless the user separately asks.

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.

Check your setup, free