document-spf-use-case
GitHub用于记录SPF用例，明确交付场景、功能组成、状态及验证信息。在用户明确要求时创建或修订条目，区分现状与计划，更新关联项并标记缺失要素。
触发场景
安装
npx skills add videojs/video.js --skill document-spf-use-case -g -y
SKILL.md
Frontmatter
{
"name": "document-spf-use-case",
"description": "Document an SPF use-case record. Use when the user explicitly requests delivery scenarios, variants, relationships, status, or verification."
}
Document an SPF use case
Read references/workflow.md completely before acting; it contains the detailed composition, evidence, cascade, and validation workflow.
Confirm that the user explicitly requested creation or revision of the entry. Do not create adjacent feature, use-case, design, or decision records discovered during the workflow; surface them as candidates instead.
Read internal/design/spf/use-cases/README.md, its decomposition rubric, related feature entries, a strong neighboring use case, and current implementation/tests.
- Describe the delivery scenario and the feature additions, removals, swaps, or tuning that compose it.
- Separate current behavior from proposed direction and decisions still needed; label missing constituent features explicitly.
- For shipped variants, retain composition decisions and current source pointers. For future variants, retain the scenario, boundaries, and evidence required before implementation.
- Update directly affected entries only when their facts changed; verify links and relationship symmetry.
Do not duplicate feature definitions, code mechanics, phase tables, or progress logs. When the missing unit is an engine capability, identify it as a candidate for the feature registry; create that entry only if the user explicitly requests it.
Example
Input: “Document low-latency live playback as a composed use case.”
Output: A compact delivery-focused entry naming composition, current status, missing prerequisites, constraints, and source evidence.
版本历史
- 8a0a3d8 当前 2026-10-20 08:02
