---

name: rfc-generator description: Generate RFC (Request for Comments) documents through guided conversation with engineers. Use when someone wants to create an RFC, write a technical proposal, document a system design, or draft a technical spec. Triggers include “write an RFC”, “create a proposal”, “help me document this design”, “technical spec”, or “I need to propose a change”.

RFC Generator

Generate RFC documents through focused conversation. The goal is no-fluff: ask only what’s needed, skip irrelevant sections, produce a clean document.

Conversation Flow

Phase 1: Core Understanding (Always Required)

Start by understanding the proposal at a high level:

1. What are you proposing? Get the one-sentence summary.
2. What problem does this solve? Understand the context and pain points.
3. What’s the goal? Clarify what success looks like.

After these answers, you should be able to fill: Name, Summary, Context, Goals.

Phase 2: Design Details (Adapt to Complexity)

Based on the proposal type, ask targeted follow-ups:

For system/architecture changes:

• What’s the high-level design?
• What assumptions are you making?
• Where might this break or cause problems?
• Are there API changes?

For process/workflow changes:

• What changes and what stays the same?
• Who’s affected?
• What’s the rollout approach?

For new features/products:

• What does the user experience look like?
• What are the technical requirements?
• What’s explicitly out of scope?

Phase 3: Security Check (If Applicable)

If the change touches any of these areas, probe further:

• Authentication/authorization
• User data collection or handling
• External dependencies
• New infrastructure
• APIs (new or modified)

Use the security checklist in

to determine if security review is needed.

Phase 4: Practical Details (As Needed)

Only ask if relevant and not already covered:

• Alternatives considered?
• Rough complexity/timeline estimate?
• Testing approach?
• How will you know it’s working? (monitoring)

Conversation Style

• Ask 1-3 questions at a time, not a wall of questions
• Summarize understanding before moving to the next phase
• Skip sections that don’t apply—not every RFC needs all sections
• Be direct: “I have what I need for the design section. Quick question on security…”
• Offer to generate early: Once you have enough for a useful draft, offer to generate it and iterate

Output Generation

When ready to generate, produce markdown following the structure in

.

Key principles:

• Include only sections with actual content
• No placeholder text or “N/A” sections—just omit them
• Keep the metadata table at the top
• Use clear, direct language throughout

After generating, ask: “Want me to expand any section or adjust anything?”

Template Reference

See

for the full RFC structure and field descriptions.