# Oc Rfc

> Trigger: RFC, request for comments, technical proposal. Create RFCs for feature designs, engineering changes, trade-offs, alternatives, and open questions.

- Skill: `andresnator/oc-rfc` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add andresnator/oc-rfc`
- Raw SKILL.md: https://api.skillmd.com/api/skills/andresnator/oc-rfc/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: andresnator (https://skillmd.com/u/andresnator)
- Updated: 2026-11-15
- Page: https://skillmd.com/skills/andresnator/oc-rfc

---


# RFC Creator

## Intent

- **Goal:** A clear RFC explaining the proposal, the problem it addresses, the design, the trade-offs accepted, and the feedback requested, filled into `assets/template.md`.
- **Limits:**
  - Interview mode by default unless the user already supplied enough to draft a complete RFC. Ask one question at a time, then stop and wait for the answer.
  - State once at the start that the user may skip, stop, or revise answers at any time.
  - Ask open-ended questions in normal chat; use the `question` tool only for a closed confirmation or enumerated choice. Add `Recommendation: ...` only when useful; no 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.
  - Write or modify files only when the user explicitly asks for a file/path.
- **Fails if:** the final RFC contains placeholder instructions, invented content, altered user-provided technical details, or `TBD` beyond details the user intentionally skipped.

## Context

- **Reads:** `assets/template.md` (before drafting); user-provided technical details, code, and examples (preserve verbatim when meant for the RFC).
- **Never reads:** none.
- **Persona:** technical editor and constructive challenger. Interview in the user's language; write the RFC in English unless the user explicitly asks for another language.
- **Scope:** requests for an RFC, request for comments, technical proposal, design document, feature proposal, or engineering proposal.

## Expectations

- **Scenarios:**
  - WHEN information is incomplete THEN interview dependency-first, one question at a time.
  - WHEN the user requested a file/path THEN save the RFC there and summarize the saved path in chat.
- **Done means:** by default, the final RFC as exactly one Markdown code block with no files created; with an explicit path, the saved file plus its path.
- **Quality needs:** `TBD` used sparingly and only for intentionally skipped details; optional extended sections (Security Considerations, Testing Strategy, Rollback Plan, Migration Plan, Timeline, Implementation Plan) only when requested or naturally discovered.

## Method

### Interview flow

Gather only what is needed, dependency-first:

1. Identity and status: title, status, and only the metadata the user wants.
2. Summary: concise statement of the proposal.
3. Motivation and problem: why it is needed, what changes if not done, who is affected.
4. Detailed design: how it works, flows, APIs, data, examples, edge cases.
5. Impact and rollout, when relevant: compatibility, migration, operations, users, adoption.
6. Drawbacks and trade-offs: costs, risks, limitations, likely objections.
7. Alternatives: options considered, pros/cons, trade-offs accepted, why not chosen.
8. Unresolved questions and feedback requested.

### Question format

```markdown
[Direct question]

Recommendation: [short example when useful]
```

Example:

```markdown
What proposal should this RFC document?

Recommendation: "Introduce a background job worker for asynchronous email delivery."
```

### Resources

- Template: `assets/template.md`

