write-rfc

Draft RFC documents using the THV template for ToolHive repositories.

3|2|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/stacklok/toolhive-rfcs --skill write-rfc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-rfc
Source: https://github.com/stacklok/toolhive-rfcs/tree/main/.claude/skills/write-rfc
Command: npx skills add https://github.com/stacklok/toolhive-rfcs --skill write-rfc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines creating RFCs for ToolHive projects by providing a structured template and guidance to ensure consistency, alignment, and clear problem statements.

Core Features & Use Cases

  • Structured RFC templates: Generates RFC files that follow the THV naming conventions and template structure.
  • Guided workflow: Assists in collecting requirements, research steps, and formalizing proposals across toolhive-related repos.
  • Use Case: A PM or engineer drafts an RFC for a cross-project change, then uses the skill to generate the initial draft ready for review.

Quick Start

Use the write-rfc skill to start a new RFC draft named THV-XXXX-descriptive-name.md.

Frequently Asked Questions about write-rfc

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

FAQPage Schema
How do I write an RFC for a ToolHive project?

To write an RFC for a ToolHive project, use a guided skill to structure problem formulation and implementation notes. It enforces the THV RFC template, metadata requirements, and naming conventions for review-ready drafts.

What is the required structure for a ToolHive RFC proposal?

A ToolHive RFC proposal requires a consistent, reviewable structure enforced by the THV template. It includes metadata, problem formulation, research steps, and implementation notes to ensure cross-project alignment.

Can I use this RFC workflow across multiple repositories like toolhive-studio and toolhive-registry?

Yes, this RFC workflow applies across multiple repositories including toolhive, toolhive-studio, toolhive-registry, toolhive-registry-server, toolhive-cloud-ui, and dockyard for consistent cross-project proposals.

How do I name my RFC file for a ToolHive design document?

Name your RFC file using the THV naming convention format THV-XXXX-descriptive-name.md. This ensures your design document is correctly identified and ready for review within the ecosystem.

Do I need to manually format metadata when drafting a ToolHive RFC?

No, you do not need to manually format metadata when drafting a ToolHive RFC. The guided workflow enforces metadata requirements automatically, ensuring your proposal maintains alignment and clear problem statements.