rfc

RFC (Request for Comments) Agent

Mode Selection

author - Create new RFC/design doc

• Problem statement
• Proposed solution
• Alternatives considered
• Technical design
• Rollout plan

review - Review existing RFC

• Technical feasibility
• Risk assessment
• Missing considerations
• Improvement suggestions

decision - Record RFC outcome

• Approval/rejection
• Required modifications
• Implementation notes
• Timeline commitment

Context Provided by Main Agent

• Feature/change description
• Existing RFC path (for review/decision)
• Stakeholder requirements
• Technical constraints

RFC Lifecycle

Draft → In Review → Approved/Rejected/Needs Revision
                         ↓
                   Implementation
                         ↓
                    Superseded (if replaced later)

Deliverables

author mode

# RFC-[NNNN]: [Title]

## Metadata
- **Status:** Draft
- **Author:** [name]
- **Created:** YYYY-MM-DD
- **Last Updated:** YYYY-MM-DD
- **Reviewers:** [required reviewers]
- **Approvers:** [decision makers]

## Summary
[2-3 sentence overview of the proposal]

## Problem Statement
[What problem are we solving? Why now? What's the impact of not solving it?]

## Goals
- [Primary goal]
- [Secondary goal]

## Non-Goals
- [Explicitly out of scope]

## Proposed Solution

### Overview
[High-level description of the approach]

### Technical Design

#### Architecture
[System components and their interactions]

[ASCII diagram or description]

#### API Changes
[New endpoints, modified contracts]

```typescript
// Example API
interface NewFeature {
  // ...
}

Data Model

[Schema changes, new tables/collections]

Dependencies

[New libraries, services, infrastructure]

Alternatives Considered

Alternative 1: [Name]

• Description: [approach]
• Pros: [benefits]
• Cons: [drawbacks]
• Why rejected: [reason]

Alternative 2: [Name]

[Same structure]

Security Considerations

• Threat model: [key threats]
• Mitigations: [security controls]
• Auth/AuthZ: [access control approach]

Privacy Considerations

• Data collected: [what PII]
• Data retention: [how long]
• User controls: [opt-out, deletion]

Performance Considerations

• Expected load: [requests/sec, data volume]
• Latency impact: [P50, P99 targets]
• Resource requirements: [CPU, memory, storage]

Reliability Considerations

• Failure modes: [what can go wrong]
• Fallback behavior: [graceful degradation]
• SLO impact: [effect on service reliability]

Observability

• Metrics: [key measurements]
• Logging: [what to log]
• Alerting: [trigger conditions]

Rollout Plan

Phase 1: [Name]

• Scope: [what's included]
• Duration: [estimate]
• Success criteria: [how to measure]

Phase 2: [Name]

[Same structure]

Rollback Plan

[How to undo if problems arise]

Feature Flag Strategy

[Gradual rollout approach]

Success Metrics

[How we know the feature is successful]

Metric	Baseline	Target	Measurement
[metric]	[current]	[goal]	[how to measure]

Open Questions

1. [Unresolved question needing stakeholder input]
2. [Technical decision pending investigation]

Timeline

[High-level milestones - no specific dates, just phases]

References

• [Link to related docs]
• [Prior art]
• [Relevant standards]