skills.rest
cuemby
cuembyOFFICIAL
Explore all skills by this author →
Website𝕏@cuembyGitHub

create-rfd

Create Request for Discussion documents with structured sections and lifecycle states.

Updated Feb 17, 2026
Search Tags:#architecture#decision making#documentation#consensus building#technical proposal#rfd
One-click install
npx skills add https://github.com/cuemby/cloud-marketplace --skill create-rfd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-rfd
Source: https://github.com/cuemby/cloud-marketplace/tree/main/.claude/skills/create-rfd
Command: npx skills add https://github.com/cuemby/cloud-marketplace --skill create-rfd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting technical decisions, exploring alternatives, and building consensus before implementation, ensuring clear rationale and shared understanding.

Core Features & Use Cases

  • Structured Documentation: Creates Request for Discussion (RFD) documents with clear sections for problem, options, and rationale.
  • Decision Rationale Capture: Preserves the "why" behind technical choices for future reference.
  • Workflow Integration: Guides users through discovery, research, and state transitions (Ideation, Discussion, Published, Committed, Abandoned).
  • Use Case: When deciding between two database technologies, use this Skill to create an RFD that outlines the pros and cons of each, facilitating a team discussion and a well-documented final decision.

Quick Start

Use the create-rfd skill to start documenting a new technical decision about API caching strategies.

Frequently Asked Questions about create-rfd

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

FAQPage Schema
How do I document technical decisions and explore alternatives before implementation?▼

To document technical decisions, create a Request for Discussion (RFD) with structured sections for the problem, options, and rationale to preserve the reasoning behind choices before implementation begins.

What is an RFD and when do I need it for architecture decision making?▼

An RFD is a Request for Discussion document used to capture technical decision-making rationale. You need it when building consensus around architecture choices to ensure a shared understanding of the problem space.

How do I manage the lifecycle of a technical proposal from ideation to commitment?▼

Manage technical proposal lifecycles by transitioning RFD documents through defined states: Ideation, Discussion, Published, Committed, or Abandoned, ensuring systematic tracking of consensus building.

Can I transition an architecture decision directly into product requirement planning?▼

Yes, the RFD workflow integrates directly with PRD creation workflows, allowing a seamless transition from finalized technical decisions into implementation planning.

What's the best way to build consensus on database technology choices for a team?▼

The best way to build consensus on database choices is to create an RFD outlining the pros and cons of each option, which facilitates structured team discussion and yields a well-documented final decision.

Related Skills

Explore More Software Engineering Skills→
SriRamkunamsettySriRamkunamsetty

one-three-one-rule

Generate a 1-3-1 decision brief with problem, options, and recommendation.

Community
Advanced
openkaidenopenkaiden
3

work-on-issue

Analyze GitHub issues and pull requests to generate structured implementation plans.

Official
Advanced
ar4mirezar4mirez
7

create-rfd

Create and manage Requests for Discussion documents with structured lifecycle states.

Community
Advanced
mvandermeulenmvandermeulen
2

architecture-decision-records

Standardize creation and maintenance of Architecture Decision Records with predefined templates.

Community
Intermediate