Rfc
Trigger: RFC, request for comments, technical proposal. Create RFCs for feature designs, engineering changes, trade-offs, alternatives, and open questions.From its SKILL.md
npx -y skills add andresnator/agents-orchestrator --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.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
3.8 KB, 723 tokens by cl100k_base, as published. Nobody here has run it
RFC Creator
Create clear RFCs that explain a proposal, the problem it addresses, the design being discussed, the trade-offs accepted, and the feedback requested.
Activation Contract
Use this skill when the user asks for an RFC, request for comments, technical proposal, design document, feature proposal, or engineering proposal.
Default to interview mode unless the user already supplied enough information to draft a complete RFC. Ask interview questions in the user's language. RFC artifact language is English unless the user explicitly asks for another language.
Hard Rules
- Ask one question at a time in interview mode.
- After asking each interview question or challenge, stop and wait for the user's answer before continuing.
- State once at the start of the interview that the user may skip, stop, or revise answers at any time.
- Keep a dynamic estimated remaining-question counter; update it when dependencies appear or disappear.
- Recommend short example answers when they help the user respond.
- Format interview questions as readable Markdown, not plain text.
- Constructively challenge vague, contradictory, or rationale-free answers before drafting; proceed if the user explicitly says to continue anyway.
- Do not invent design details, alternatives, drawbacks, risks, unresolved questions, or rationale. Ask when important details are missing.
- Preserve user-provided technical details, code, and examples verbatim when they are meant to appear in the RFC.
- Use
TBDsparingly and only when the user intentionally skips a detail. - Write or modify files only when the user explicitly asks for a file/path.
Interview Flow
Gather only what is needed, dependency-first:
- Identity and status: title, status, and only the metadata the user wants to include.
- Summary: concise statement of the proposal.
- Motivation and problem: why this is needed, what changes if it is not done, and who is affected.
- Detailed design: how it works, important flows, APIs, data, examples, and edge cases.
- Impact and rollout, when relevant: compatibility, migration, operations, users, or adoption path.
- Drawbacks and trade-offs: costs, risks, limitations, and reasons someone might object.
- Alternatives: other approaches considered, their pros/cons, the trade-offs accepted, and why they were not chosen.
- Unresolved questions and feedback requested.
Question format:
### Question N — [focused question]
**Recommended answer:** [short example when useful]
**Why this matters:** [brief reason]
**Estimated remaining questions:** ~M
Mini example:
### Question 1 — What proposal should this RFC document?
**Recommended answer:** "Introduce a background job worker for asynchronous email delivery."
**Why this matters:** The title and scope anchor every later design, trade-off, and review question.
**Estimated remaining questions:** ~6
Optional extended sections may be included only when requested or naturally discovered: Security Considerations, Testing Strategy, Rollback Plan, Migration Plan, Timeline, or Implementation Plan.
Output Contract
Read assets/template.md before drafting and fill that structure.
By default, return the final RFC as exactly one Markdown code block and do not create files. If the user explicitly requested a file/path, save the RFC there and summarize the saved path in chat.
Never leave placeholder instructions in the final RFC. If the user intentionally skips a required detail, use TBD sparingly and only for that skipped detail.
Reference
- Template:
assets/template.md
What ships with it: 1 file
1.4 KB alongside SKILL.md
assets/
- template.md1.4 KB