← ClaudeAtlas

rfclisted

Interactive skill for creating RFC (Request for Comments) documents as Markdown files. Use this skill whenever the user wants to create an RFC, write a technical proposal, draft a design document, create a technical spec, or write a feature proposal. Triggers include: 'RFC', 'rfc', 'request for comments', 'design doc', 'technical proposal', 'feature proposal', 'tech spec', 'architecture proposal', 'engineering proposal', or any request to document a technical decision with sections like motivation, design, alternatives, and drawbacks. This skill guides the user through an interactive interview process, asking questions step by step, and then generates a polished RFC Markdown file. Use this even if the user just says 'I want to propose a new feature' or 'I need to document a technical decision' — these are RFCs in disguise. También se activa en castellano: "RFC", "propuesta técnica", "documento de diseño", "especificación técnica", "propuesta de arquitectura", "propuesta de ingeniería", "crear un RFC", "escrib
andresnator/agents-orchestrator · ★ 0 · Data & Documents · score 62
Install: claude install-skill andresnator/agents-orchestrator
# RFC Creator — Interactive Interview & Markdown Generator ## Overview This skill creates professional RFC (Request for Comments) documents by guiding the user through a structured interview. Instead of asking the user to fill in a template, the agent conducts a conversational interview, collecting information piece by piece, and then assembles a polished Markdown RFC at the end. The goal is to make writing an RFC feel like a conversation, not paperwork. ## Interview Flow The interview has **7 phases**. Walk the user through them one at a time. After each phase, summarize what you captured and confirm before moving on. When a question has clear bounded options, present those options plainly in chat and ask the user to choose one; use open-ended prose questions for everything else. **Important behavioral notes:** - Ask one phase at a time. Do not dump all questions at once. - After the user answers, briefly reflect back what you understood and confirm it before proceeding. - If the user gives a vague answer, ask a clarifying follow-up — but don't be annoying about it. One follow-up is enough; if they're still vague, work with what you have. - If the user says "skip" or "not sure yet" for any section, mark it as TBD in the final document and move on. - The user can say "go back" at any time to revise a previous section. ### Phase 1: Identity & Metadata Collect the basic metadata for the RFC header. Ask (open-ended): - **Feature name**: "What's the name or short identif