rfc

Formalize Video.js 10 direction proposals with structured RFC documents.

888|82|Updated Aug 13, 2025
One-click install
npx skills add https://github.com/videojs/v10 --skill rfc-videojs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rfc
Source: https://github.com/videojs/v10/tree/main/.claude/skills/rfc
Command: npx skills add https://github.com/videojs/v10 --skill rfc-videojs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RFCs formalize buy-in for Video.js 10 direction proposals, ensuring alignment across teams and faster, traceable decisions.

Core Features & Use Cases

  • Structured governance: Create, review, and track RFCs for API changes, architecture decisions, and DX improvements.
  • Lifecycle-aware process: Manage drafts, reviews, iterations, and final approvals with clear next steps.
  • Reference & reproducibility: Link design context, alternatives, and decisions to a stable record for future reference.

Quick Start

Start by creating a new RFC document in the rfc/ directory with a descriptive title and frontmatter, then open a discussion thread for review.

Frequently Asked Questions about rfc

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

FAQPage Schema
How do I write an RFC for Video.js architecture decisions?

Writing an RFC for Video.js architecture decisions involves creating a document in the rfc/ directory with frontmatter metadata and a structured proposal body. This formalizes cross-team buy-in for API changes and developer-experience proposals.

What is the RFC lifecycle for design docs in Video.js?

The RFC lifecycle for Video.js design docs spans from draft through review to final acceptance. This process tracks iterations and defines clear next steps for managing proposals and architecture decisions.

When do I need an RFC proposal for API changes?

An RFC proposal for API changes is needed when cross-team agreement is required for Video.js 10 direction. RFCs formalize buy-in for architecture decisions and developer-experience improvements to ensure traceable decisions.

How to start a design doc discussion for Video.js 10 direction?

Starting a design doc discussion for Video.js 10 direction requires creating a new RFC document with a descriptive title and frontmatter in the rfc/ directory, then opening a discussion thread for review.

What metadata is required for a Video.js RFC proposal?

A Video.js RFC proposal requires enforced frontmatter metadata and a structured proposal body. This structure links design context, alternatives, and decisions to a stable record for reference and reproducibility.