rfc-writer

Generate and manage RFC documents with RFC 2119 normative clauses.

239|12|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/govctl-org/govctl --skill rfc-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfc-writer
Source: https://github.com/govctl-org/govctl/tree/main/.claude/skills/rfc-writer
Command: npx skills add https://github.com/govctl-org/govctl --skill rfc-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users write well-structured Request for Comments (RFCs) with normative clauses, ensuring clarity and adherence to governance standards in software development.

Core Features & Use Cases

  • RFC Creation: Generate new RFC documents with a specified title.
  • Clause Management: Add, edit, and manage individual clauses within an RFC, specifying their type (informative/normative) and content.
  • Standard Enforcement: Enforces the use of RFC 2119 keywords (MUST, SHOULD, MAY) and provides a checklist for writing high-quality, testable requirements.
  • Use Case: When starting a new feature that requires formal specification, use this Skill to create an RFC and define its core requirements using precise, normative language.

Quick Start

Use the rfc-writer skill to create a new RFC titled "New Authentication Flow".

Frequently Asked Questions about rfc-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a structured RFC with normative clauses for software governance?

To write an RFC, generate a new document with a title, then add and edit individual clauses while specifying their type as informative or normative. This ensures precise requirement definition and rationale inclusion for auditable specifications.

What are RFC 2119 keywords and how are they used in requirement specifications?

RFC 2119 keywords like MUST, SHOULD, and MAY define normative requirement levels in specifications. Enforcing these keywords ensures high-quality, testable requirements that adhere to governance standards.

When do I need to use an RFC format for software feature development?

You need an RFC format when starting a new feature that requires formal specification and governance. It facilitates defining core requirements using precise, normative language to maintain auditable documentation.

Can I manage individual clauses within an RFC document?

Yes, you can add, edit, and manage individual clauses within an RFC document. This clause management capability allows you to specify whether each clause is informative or normative and include rationale for maintainable specifications.

What is the best way to ensure my requirements are testable and auditable?

The best way to ensure testable requirements is to use a checklist during RFC creation and enforce RFC 2119 standard keywords. This generates structured, normative clauses that guarantee clarity and adherence to governance standards.