Dev Rfc

This does what RFC and design doc templates try to do, but as an interactive skill that picks the right structure for your situation. It distinguishes between pre-build proposals (should we build this?), architecture docs (how does the existing system work?), and changes to existing systems. The guidance on approaches is solid: it pushes you to represent alternatives fairly instead of strawmanning them, and it wants concrete SLAs with numbers instead of "high availability" hand-waving. Includes review checklists and optional feedback UI. Most useful when you need stakeholder alignment on something non-trivial or when onboarding engineers to a complex codebase. The template scaling for small/medium/large projects keeps you from over-documenting a two-day change.

skills.sh installs: 279
GitHub stars: 222
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add pproenca/dot-skills --skill dev-rfc --agent claude-code

Installs into .claude/skills of the current project.

Files

Dev RFC Skill

Write RFCs and technical proposals that serve two purposes: aligning stakeholders on what to build and why (RFCs), and helping engineers understand how a system works (architecture docs). Most real proposals blend both — the skill helps you pick the right sections for the situation.

Reference Templates

Read references/template.md for the three structural templates:

RFC — for pre-build alignment. Focuses on abstract, approaches (with fair comparison), service SLAs, observability, and rollout plan.
Architecture Doc — for documenting built systems. Focuses on diagrams, source tree, data flow, design philosophy.
One-Pager — for small changes (< 1 week). Problem, Proposed Solution, Rollout. ~20 lines.