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.