What problem does it solve?
Implementing a documented SPF engine feature without a disciplined workflow leads to code that drifts from the feature doc, misses open questions, skips conventions, and leaves the feature registry stale. This Skill enforces a structured disambiguation, planning, TDD, and registry-update workflow so implementations match the documented scope.
Core Features & Use Cases
- Feature disambiguation and routing: Resolves whether a request maps to an existing feature doc, a use case, or cluster policy before any code is written.
- Destination-architecture framing: Sketches the cluster's target shape and assesses fold-in candidates (full, partial, design-with-in-mind, ignore) so the implementation fits the larger architecture.
- Test-driven chunked implementation: Splits scope into testable state, behavior, composition, adapter, and documentation chunks, each landing with a failing test first.
- Registry synchronization: Updates the feature doc's Status, Implementation surface, and Verification sections as code lands.
- Use Case: Given a request like "implement the smallest useful increment of timeline discontinuity support," the Skill reads the feature doc, resolves open questions, implements the minimal end-to-end increment with tests, and reports deferred scope.
Quick Start
Ask the agent to implement the smallest useful increment of a named SPF feature from the registry, for example "implement audio-abr Phase 1".
