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
- viniciusamelio/skillstheir own version, first seen Nov 8, 2026
- dimsedra/skillstheir own version, first seen Nov 8, 2026
- devjiwonchoi/skillstheir own version, first seen Nov 8, 2026
- wilanis/wilanis-jstheir own version, first seen Oct 17, 2026
- arfar-x/agent-skillstheir own version, first seen Oct 12, 2026
- rlajous/claude-code-commandstheir own version, first seen Aug 28, 2026
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.
SentrySkillreview
Fixture review skill.
Also in 4 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- AlemTuzlak/skills★ 45same name
- rlajous/claude-code-commands★ 30same name
- arfar-x/agent-skills★ 14same name
- devjiwonchoi/skills★ 2same name
- dimsedra/skills★ 2same name
- wilanis/wilanis-js★ 1same name
- dil-landrasi/skills★ 0same name
- stevancris/sre-ai-agent★ 0same name
- un1tz3r0/rfc-skill★ 0same name
- viniciusamelio/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- briefSkill
- closeoutSkill
- decisionSkill
- deskSkill
- doctorSkill
- editorSkill
- grillSkill
- handoffSkill
- morningSkill
- openSkill
- recentSkill
- researchSkill
- rfcSkill
- setupSkill
- shapeSkill
- specSkill
- weekly-reviewSkill
- briefSkill
- closeoutSkill
- decisionSkill
- deskSkill
- doctorSkill
- editorSkill
- grillSkill
- handoffSkill
- morningSkill
- openSkill
- recentSkill
- researchSkill
- setupSkill
- shapeSkill
- specSkill
- weekly-reviewSkill
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
- Very specific: line 10
Read the owner binder, active workstream, related decisions, and library/templates/rfc.md.
- Distinctive: line 14
Write new RFCs inside the owner binder.
- Distinctive: line 17
If linking the artifact changes the workstream, create a receipt only for that workstream revision transition.
- Distinctive: line 20
Do not present personal preference as repository policy or manufacture consensus.
“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.
Files
<!-- Generated from .agents/skills/rfc/SKILL.md; source-sha256: bf5db6176e7aad68dec581c4e349c4229d6ecfa7a7997cde032e463b6570535a. -->RFC
- Read the owner binder, active workstream, related decisions, and
library/templates/rfc.md. - Define the problem, audience, constraints, goals, non-goals, and decision requested.
- Describe the recommended design at the level needed to evaluate it. Include alternatives, tradeoffs, failure modes, compatibility, rollout, and verification only where material.
- Make open questions explicit and assign an owner or decision trigger.
- Write new RFCs inside the owner binder; revise existing RFCs in place. Link current execution state rather than duplicating it.
- 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.
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
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.