Generate request-for-comments documents with standardized sections for proposal review.
npx skills add https://github.com/dhnt/dhnt --skill write-rfc-dhnt
Please help me install this Agent Skill. Skill: write-rfc Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/plan/write-rfc Command: npx skills add https://github.com/dhnt/dhnt --skill write-rfc-dhnt
It helps teams document and align on substantial, high-impact proposals before committing to implementation, reducing the risk of expensive rework and improving decision traceability.
Author an RFC for your proposal at the plan phase using the /write-rfc skill, following the required section structure and sending it for review with a deadline.
High-intent search queries and answers about installing and using this skill.
You need an RFC for substantial changes affecting public APIs, data models, external contracts, or multi-team interfaces where the cost of disagreement or reversal is high. It secures stakeholder buy-in before implementation begins.
A standard RFC includes title, status, authors, problem statement with no-op cost, goals, non-goals, proposed solution, alternatives, migration rollout, security, backwards compatibility, observability, open questions, and decision criteria.
Structure the rollout plan by detailing migration steps, backwards compatibility measures, and observability requirements. The RFC process requires resolving every comment against this plan before final acceptance.
The RFC process encourages parallel drafting of alternatives to evaluate approach tradeoffs. It uses deadline-based feedback and requires resolving every comment before acceptance to keep reviewers informed and engaged.
Yes, this RFC format applies to multi-team interfaces and internal cross-team changes. It helps stakeholders evaluate implementation impact and approach tradeoffs before any code lands.
The no-op cost documents the expense or risk of not implementing the proposal. Including this cost in the RFC problem statement ensures stakeholders understand the baseline impact of leaving the system unchanged.
nist0Generates a structured RFC document with problem, goals, alternatives, risks, and rollout plans.
udecodeAnalyze repository evidence to propose architecture, migration, or benchmark decisions.
heymishyAutomate scalable operating model design for skills pipeline rollout.
garethrhughesDesign technical changes with Mermaid diagrams and acceptance criteria.
