agentleFS
ayleeaylee/agent-os/.agents/skills/rfc/SKILL.md

rfc

Skill0 starsChanged 4 months agoMITView on GitHub

Write or revise a request for comments. Use when the user asks to propose an approach, expose tradeoffs, invite debate, or resolve an architectural direction; use decision after a choice is settled.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review.

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.
  • SentrySkill

    review

    Fixture review skill.

    Also in 4 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 10 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:

    Read the owner binder, active workstream, related decisions, and library/templates/rfc.md.

    line 8
  2. Distinctive:

    Write new RFCs inside the owner binder.

    line 12
  3. Distinctive:

    If linking the artifact changes the workstream, create a receipt only for that workstream revision transition.

    line 15
  4. Distinctive:

    Do not present personal preference as repository policy or manufacture consensus.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 10 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

RFC

  1. Read the owner binder, active workstream, related decisions, and library/templates/rfc.md.
  2. Define the problem, audience, constraints, goals, non-goals, and decision requested.
  3. Describe the recommended design at the level needed to evaluate it. Include alternatives, tradeoffs, failure modes, compatibility, rollout, and verification only where material.
  4. Make open questions explicit and assign an owner or decision trigger.
  5. Write new RFCs inside the owner binder; revise existing RFCs in place. Link current execution state rather than duplicating it.
  6. Link the RFC from the workstream artifact index when it affects active work. Do not create a receipt for the RFC edit.

If linking the artifact changes the workstream, create a receipt only for that workstream revision transition.

Do not present personal preference as repository policy or manufacture consensus.

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.