rfc-process
Skill2 starsChanged 7 days agoMITView on GitHub
Write, number, and advance RFCs in the house shape used across amkisko libraries. Use when adding an RFC, claiming an id, copying the template, mapping status, flattening an RFC tree, or aligning a repo to this process.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-artifactSkill
- agent-discoverySkill
- agent-run-supervisionSkill
- api-contract-migrationSkill
- changelog-updateSkill
- change-reviewSkill
- ci-reviewSkill
- claims-auditSkill
- dependency-auditSkill
- derivation-auditSkill
- durable-cacheSkill
- engineering-auditSkill
- infer-conventionsSkill
- operational-signal-intakeSkill
- planned-releaseSkill
- preferred-stackSkill
- pressure-benchmarkingSkill
- public-surface-reconSkill
- security-auditSkill
- session-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read rfc-process.md in this skill directory for claim, template, types, statuses, length, and isolation.
- Very specific: line 19
Keep existing RFC numbers.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
RFC process
Read rfc-process.md in this skill directory for claim, template, types, statuses, length, and isolation. Read references/template.md when copying or replacing rfcs/0000-template.md.
Quick reference
read rfcs/README.md -> claim ids/NNNN -> copy template -> omit empty sections -> PR rfc: NNNN title -> implementation cites RFC-NNNNKeep existing RFC numbers. Project bands and extra tests stay in that repo's rfcs/README.md. Product RFCs specify a design (suggestion, motivation, specification, effects, alternatives, prior art). Version numbers belong in changelogs.
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.