Run any Skill in Manus with one click

rfc

Stars829

Forks69

UpdatedFebruary 13, 2026 at 20:04

Write RFCs for Video.js 10. Use for proposals that need buy-in — public API changes, product direction, user-facing DX, core architecture. Triggers: "write RFC", "create RFC", "propose", "need buy-in", "architecture proposal".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

videojs

videojs/v10

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	rfc
description	Write RFCs for Video.js 10. Use for proposals that need buy-in — public API changes, product direction, user-facing DX, core architecture. Triggers: "write RFC", "create RFC", "propose", "need buy-in", "architecture proposal".

RFC

Write Request for Comments (RFC) documents for Video.js 10.

RFCs are for proposals that need buy-in from others before proceeding. For decisions you own, use a Design Doc instead (design skill, internal/design/).

Reference Material

Task	Load
Any RFC task	This file (SKILL.md)
Writing principles	`design` skill (Principles section)

When to Write an RFC

Write an RFC when:

Changes public API surface
Affects product direction
Affects user-facing developer experience
Significant changes to core architecture
Needs buy-in from others

Use a Design Doc instead when:

Architectural decisions in your area
Internal implementation choices
Design patterns or component specs you own

Skip both for:

Bug fixes
Small features in one package
Implementation details
Documentation updates

See rfc/README.md for status lifecycle, branch workflow, and relationship to implementation plans.

Checklist

Before finalizing an RFC:

Problem clearly stated — why is this worth solving now?
Solution is high-level — details come in Design Docs after approval
Alternatives considered with pros/cons
Trade-offs are explicit
Open questions listed
Next steps clear (what happens if approved)
Frontmatter has status: draft

Process

Identify need — Does this actually need buy-in? If not, write a Design Doc
Draft proposal — Focus on problem and approach, not implementation details
List alternatives — Show you've considered other options
Surface trade-offs — Be honest about costs
Gather feedback — Share with affected parties
Iterate — Update based on feedback
Get approval — Move to status: accepted when agreed
Document — Write Design Doc with full details after approval

Writing Principles

For detailed writing guidance (progressive disclosure, conciseness, etc.), see the design skill's Principles section. The same principles apply to RFCs.

Need	Use
Decisions you own	`design` skill
API design principles	`api` skill
Building UI components	`component` skill
Writing documentation	`docs` skill

More from this repository

same repository

spf-implement-feature

videojs/v10

Implement a feature documented in the SPF feature registry. Consumes a feature doc at internal/design/spf/features/<name>.md and produces the engine-side code: new behaviors, updates to existing behaviors, media-layer / network-layer primitives, and tests. The implementation analog of /spf-document-feature (which produces the doc; this consumes it). Walks through resolving the doc's open questions before coding, maps phases to discrete chunks, applies the SPF conventions catalog, routes to downstream skills (/spf-create-behavior, /spf-update-behavior, /refactor-behavior) per chunk shape, and updates the feature doc's Status / Implementation surface / Verification sections as code lands. Triggers: "implement feature", "implement SPF feature", "build feature", "code feature", "scope feature implementation", "implement <feature-name>".

2026-06-04829

spf-create-behavior

videojs/v10

Create a new SPF behavior with conventions-aligned shape. Walks through purpose articulation (carries /refactor-behavior's purpose-first discipline), signal type choice, slot map design, composition placement, cleanup pattern selection, test placement, and engine wiring. Distinct from /refactor-behavior (which modifies an existing behavior preserving its purpose) and /spf-update-behavior (which modifies an existing behavior whose purpose is changing). Triggers: "create behavior", "new behavior", "create SPF behavior", "add behavior", "scaffold behavior", "new SPF behavior".

2026-05-27829

spf-document-use-case

videojs/v10

Produce or update an entry in the SPF use-case-composition registry at internal/design/spf/use-cases/. Triangulates context from multiple sources (Notion, GitHub, pasted writeups, existing use-case docs, constituent feature docs, codebase), grounds the use case in the four composition mechanisms (subtract / add / alternative-impl / alternative-default-config), applies use-case-specific cross-cutting concern checks, drafts the doc at the appropriate definition depth, and cascades narrow updates to constituent feature docs and sibling use cases. Triggers: "document use case", "register use case", "use case doc", "update use case doc", "deepen use-case stub", "new SPF use case", "use case composition", "draft use-case registry entry", "new use case composition".

2026-05-27829

spf-implement-use-case

videojs/v10

Implement a use-case composition documented in the SPF use-case-composition registry. Consumes a use-case doc at internal/design/spf/use-cases/<name>.md and produces the engine-side code: a variant engine factory, a parallel adapter, composition wiring, use-case-specific behaviors (if any), and tests. The implementation analog of /spf-document-use-case (which produces the doc; this consumes it). Walks through disambiguation + routing (verify the request is actually a use case, check constituent-feature implementation status), resolves the doc's open questions with the user, maps phases to chunks, routes to downstream skills (/spf-implement-feature for unimplemented constituents, /spf-create-behavior, /spf-update-behavior, /refactor-behavior), and updates both the use-case doc and constituent feature docs as code lands. Treats the use-case doc as a starting point for planning, not a hardened specification. Triggers: "implement use case", "implement SPF use case", "implement use-case composition", "build use ca

2026-05-27829

spf-update-behavior

videojs/v10

Update an existing SPF behavior whose purpose is changing or expanding. Distinct from /refactor-behavior, which preserves purpose — this skill handles cases where the behavior gains new responsibility (new state slot to react to, new lifecycle phase, new constraint, new code path). Carries /refactor-behavior's purpose-first discipline applied to the *purpose change*. Triggers: "update behavior", "extend behavior", "modify behavior", "change behavior purpose", "expand behavior responsibility".

2026-05-27829

spf-document-feature

videojs/v10

Produce or update an entry in the SPF feature registry at internal/design/spf/features/. Triangulates context from multiple sources (Notion, GitHub, pasted writeups, existing feature docs, codebase), grounds the feature in the cluster heuristics, applies cross-cutting concern checks, drafts the doc at the appropriate definition depth, and cascades narrow updates to related feature docs. Triggers: "document feature", "register feature", "feature doc", "update feature doc", "deepen feature stub", "draft feature registry entry", "new SPF feature".

2026-05-21829

name	rfc
description	Write RFCs for Video.js 10. Use for proposals that need buy-in — public API changes, product direction, user-facing DX, core architecture. Triggers: "write RFC", "create RFC", "propose", "need buy-in", "architecture proposal".

RFC

Write Request for Comments (RFC) documents for Video.js 10.

RFCs are for proposals that need buy-in from others before proceeding. For decisions you own, use a Design Doc instead (design skill, internal/design/).

Reference Material

Task	Load
Any RFC task	This file (SKILL.md)
Writing principles	`design` skill (Principles section)

When to Write an RFC

Write an RFC when:

Changes public API surface
Affects product direction
Affects user-facing developer experience
Significant changes to core architecture
Needs buy-in from others

Use a Design Doc instead when:

Architectural decisions in your area
Internal implementation choices
Design patterns or component specs you own

Skip both for:

Bug fixes
Small features in one package
Implementation details
Documentation updates

See rfc/README.md for status lifecycle, branch workflow, and relationship to implementation plans.

Checklist

Before finalizing an RFC:

Problem clearly stated — why is this worth solving now?
Solution is high-level — details come in Design Docs after approval
Alternatives considered with pros/cons
Trade-offs are explicit
Open questions listed
Next steps clear (what happens if approved)
Frontmatter has status: draft

Process

Identify need — Does this actually need buy-in? If not, write a Design Doc
Draft proposal — Focus on problem and approach, not implementation details
List alternatives — Show you've considered other options
Surface trade-offs — Be honest about costs
Gather feedback — Share with affected parties
Iterate — Update based on feedback
Get approval — Move to status: accepted when agreed
Document — Write Design Doc with full details after approval

Writing Principles

For detailed writing guidance (progressive disclosure, conciseness, etc.), see the design skill's Principles section. The same principles apply to RFCs.

Need	Use
Decisions you own	`design` skill
API design principles	`api` skill
Building UI components	`component` skill
Writing documentation	`docs` skill