Generate structured RFC documents for cross-team technical proposals.
npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-rfc-jerelvelarde
Please help me install this Agent Skill. Skill: create-rfc Source: https://github.com/jerelvelarde/chalk-skills/tree/main/skills/create-rfc Command: npx skills add https://github.com/jerelvelarde/chalk-skills --skill create-rfc-jerelvelarde
Generate structured RFC documents to capture and socialize significant cross-team technical proposals.
Create a new RFC file at .chalk/docs/engineering/<number>rfc<slug>.md with a concrete proposal, a succinct summary, and a defined 5- to 10-day review period.
High-intent search queries and answers about installing and using this skill.
You need an RFC for cross-team engineering proposals that affect multiple teams or core infrastructure. It standardizes significant technical decisions by enforcing a formal review period and required reviewers to accelerate alignment.
A design proposal for engineering teams should include Summary, Motivation, Detailed Design, Review Plan, and formal acceptance criteria. These sections ensure cross-team technical proposals are thoroughly documented and reviewed.
You structure an RFC file by generating a markdown document under your engineering docs directory, named with a number and snake_case slug, containing sections for Summary, Motivation, Detailed Design, Review Plan, and acceptance criteria.
Create an RFC when your technical proposal affects multiple teams or core infrastructure. The RFC process enforces a defined 5- to 10-day review timeline and required reviewers to drive cross-team alignment on significant architectural changes.
The best way to enforce a review timeline for technical design proposals is to generate a structured RFC document that explicitly defines a 5- to 10-day review period and lists required reviewers to accelerate team alignment.
Generating an RFC document does not require any external dependencies. The process automatically creates a structured markdown file under your engineering docs directory to capture cross-team technical proposals.
camilooscargbaptistaGenerate RFC templates, review criteria, and decision logs for architecture governance.
Angel1104Converts confirmed Change Request items into standardized 10-section specification documents.
GeneralJerelCreate sequential Markdown documentation files under .chalk/docs.
GenerativeAgentsExtract and consolidate project terms into a standardized glossary at docs/glossary.md.
