Individual skill
dev-rfc
Create well-structured RFCs and technical proposals for software projects. Use this skill whenever the user wants to write an RFC, technical proposal, design doc, architecture doc, or system design overview. Also trigger when the user says things like "write an RFC", "I need to propose a new system", "create a technical proposal", "document the architecture", "write up the design", "I need a design doc", or "explain the system architecture in a doc". Even if they just say "RFC", "design doc", or "arch doc", use this skill. Covers both RFCs (proposing what to build) and architecture docs (documenting an existing codebase).
skills/.experimental/dev-rfc/SKILL.md
Source commit cf93c57cac89d6fc3e4194686000411567f5caf3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 222
- Repository last updated
- Aug 15, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
- design Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesSKILL.mdcore · 15,297 bytesassets/marked.min.jsruns · 39,903 bytesassets/mermaid.min.jsruns · 2,963,890 bytesassets/review_template.htmlasset · 56,121 bytesbun.lockasset · 2,992 bytesmetadata.jsonasset · 276 bytespackage.jsonruns · 262 bytesreferences/template.mddoc · 11,589 bytesscripts/generate_review.pyruns · 25,206 bytesscripts/generate_review.test.tsruns · 10,986 bytesscripts/generate_review.tsruns · 24,923 bytes
Read excerpt
# 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.
## Step 0: Pick the Mode
