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.
npx -y skills add pproenca/dot-skills --skill dev-rfc --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills