Loading...
Loading...
Found 3 Skills
Author RFC documents for proposed technical changes with clear problem framing, options, tradeoffs, and decision path. Use when proposal alignment and review sign-off are needed before implementation; do not use for post-decision implementation-only docs.
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).
This skill helps create RFC (Request for Comments) documents for proposing new features, architectural changes, or significant enhancements to the project. It provides templates, structure guidelines, and best practices for writing effective technical proposals. Use this skill when planning major changes that need team review and discussion. IMPORTANT: Before writing any RFC, you MUST conduct online research to survey current industry best practices, mainstream implementations, and latest trends.