implement-spf-use-case

Implements SPF use-case compositions with variant engine factories, adapters, tests, and doc updates.

931|91|Updated Aug 13, 2025
One-click install
npx skills add https://github.com/videojs/v10 --skill implement-spf-use-case
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-spf-use-case
Source: https://github.com/videojs/v10/tree/main/.agents/skills/implement-spf-use-case
Command: npx skills add https://github.com/videojs/v10 --skill implement-spf-use-case

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Turning a documented SPF use-case composition into working engine code is error-prone: requests are ambiguous between features and use cases, constituent features may be unimplemented, and docs silently drift from code. This Skill enforces a disciplined workflow that disambiguates the request, verifies constituent-feature status, and lands tested composition code.

Core Features & Use Cases

  • Disambiguation and routing: Verifies the request is actually a use case (not a feature or cluster-E policy) and routes to downstream skills like /implement-spf-feature or /document-spf-use-case when appropriate.
  • Test-first chunked implementation: Maps use-case phases to independently testable chunks (engine variant factory, adapter, composition wiring, behaviors) and implements each test-first.
  • Doc cascade updates: Updates the use-case doc and constituent feature docs with implementation surface, verification evidence, and status as code lands.
  • Use Case: Implementing the audio-only-mode-override use case by building a variant HLS engine factory, parallel adapter, and integration tests while updating the registry docs.

Quick Start

Ask the AI to implement the SPF use case documented at internal/design/spf/use-cases/<name>.md for Phase 1 scope.

Frequently Asked Questions about implement-spf-use-case

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

FAQPage Schema
How do I implement an SPF use-case composition?

Invoke the skill with a use-case name or description. It reads the use-case doc at internal/design/spf/use-cases/<name>.md, verifies constituent features are implemented, maps phases to testable chunks, and implements each chunk test-first.

How does the skill decide between a feature and a use case?

It applies the use-cases README discriminator: composition mechanisms, delivery scenario versus source-shape correctness, and constituent features. Requests that are actually features route to /implement-spf-feature instead.

What happens if a constituent feature is not implemented yet?

The skill surfaces the gap and asks the user to choose: defer the use case, implement the constituent first via /implement-spf-feature, or bundle the constituent implementation into the current pass with explicit confirmation.

Does the skill update documentation after implementation?

Yes. It updates the use-case doc's status, composition specifics, implementation surface, and verification sections, and cascades status notes to constituent feature docs. All doc revisions are explicit and surfaced to the user.

Can the implementation extend beyond the SPF engine layer?

Yes, as explicit opt-ins. The user can bundle media wrappers, HTML custom elements, React components, sandbox demos, and E2E tests; each opted-in layer becomes its own implementation chunk.