rfclisted

# 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. - Ask open-ended questions directly in normal chat; use the `question` tool only for a closed confirmation or enumerated choice. - Add a short `Recommendation: ...` line only when it helps the user respond. - Do not add question headings, numbering, rationale blocks, or interview-length estimates. - 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 exampl