What problem does it solve?
Documenting a delivery-scenario use case for the SPF playback engine is error-prone: drafts often confuse feature docs with use-case docs, default to subtractive-only composition thinking, or leave the registry internally inconsistent. This Skill enforces a disciplined nine-step workflow that triangulates sources, grounds claims in code, and keeps cross-links symmetric.
Core Features & Use Cases
- Source triangulation and scoping: Gathers context from Notion docs, GitHub issues, pasted writeups, existing use-case docs, and constituent feature docs before drafting anything.
- Composition-mechanism framing: Grounds each use case in the four composition mechanisms (subtract, add, alternative implementation, alternative default config) and applies a decomposition rubric to confirm the entry qualifies as a use case rather than a feature.
- Registry consistency cascade: After drafting, propagates narrow updates to constituent feature docs, Case-1 sibling docs, sibling use cases, and the use-cases README index, then proposes a commit structure.
- Use Case: When asked to "document low-latency live playback as a composed use case," the Skill produces a delivery-focused entry naming composition, current status, missing prerequisite features, constraints, and source evidence.
Quick Start
Ask the assistant to document a new SPF use case for your delivery scenario, providing any relevant Notion links, GitHub issues, or existing design docs as context.
