Agent Skills
› videojs/video.js
› write-rfc
write-rfc
GitHub用于起草或修订 Video.js RFC，涵盖公共 API、产品方向及架构提案。通过验证必要性、分析现状与约束、对比替代方案，生成旨在获取团队共识的正式提案文档。
触发场景
需要为公共 API 变更撰写提案
制定影响广泛的产品或架构方向
发起需要团队共识的重大技术决策
安装
npx skills add videojs/video.js --skill write-rfc -g -y
SKILL.md
Frontmatter
{
"name": "write-rfc",
"description": "Draft or revise a Video.js RFC. Use for public APIs, product direction, user-facing DX, shared architecture, or hard-to-reverse proposals needing buy-in."
}
RFC
Read rfc/README.md for the current lifecycle and format. If the user explicitly asks for an internal record instead, use a design or decision record when the author owns the choice and no wider agreement is needed.
Workflow
- Verify that an RFC is warranted; skip it for local implementation details, ordinary bugs, or already-approved work.
- Read current code, existing RFCs/design records, related issues, and relevant user evidence.
- Define the problem, affected users, constraints, goals, and explicit non-goals.
- Present the proposed direction at the level needed for agreement, not a line-by-line implementation plan.
- Compare credible alternatives and make costs, compatibility, migration, and unresolved questions explicit.
- Define how success will be evaluated and what happens after acceptance.
- Keep status
draftuntil the repository's approval process changes it.
Make public API and DX tradeoffs explicit when central. Keep implementation detail in code, or in a later design record or plan only when the user explicitly requests one.
Example
Input: “Draft an RFC for a new plugin extension model.”
Output: A draft proposal with user evidence, goals, non-goals, compatibility and migration costs, credible alternatives, open questions, and success measures.
版本历史
- 8a0a3d8 当前 2026-10-20 08:04
