Rfc
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.From its SKILL.md
npx -y skills add aylee/agent-os --skill rfcAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 180 tokens by cl100k_base, as published. Nobody here has run it
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.
What ships with it: 2 files
545 B alongside SKILL.md
agents/
- agent-os.yaml299 B
- openai.yaml246 B