Technical RFC Structure

D

Daniel Okoye

@daniel-okoye

·

Structure a technical RFC by reasoning through each section.

15 copies0 forks
Structure a technical RFC step by step.

Proposal summary:
{{proposal_summary}}

Scope: {{scope}}
Stakeholders: {{stakeholders}}

Think through systematically:

1. PROBLEM STATEMENT: What problem are we solving? Why now?

2. BACKGROUND: What context do readers need?

3. GOALS/NON-GOALS: What is in scope? What is explicitly out?

4. PROPOSED SOLUTION: What is the recommended approach?

5. ALTERNATIVES CONSIDERED: What other options exist? Why reject them?

6. DETAILED DESIGN: How does the solution work technically?

7. SECURITY CONSIDERATIONS: What are the security implications?

8. OPERATIONAL CONSIDERATIONS: What ops changes are needed?

9. MIGRATION PLAN: How do we get from here to there?

10. SUCCESS METRICS: How do we know this worked?

11. TIMELINE: What is the proposed timeline?

12. OPEN QUESTIONS: What needs further discussion?

Details

Category

Productivity

Use Cases

RFC writing assistanceTechnical proposal structureArchitecture documentation creation

Works Best With

claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared

Create your own prompt vault and start sharing