What problem does it solve?
Drafting feature documentation directly from a single source often produces entries that misread scope, claim unimplemented behavior, or drift out of sync with related docs. This Skill enforces a disciplined workflow that triangulates sources, grounds claims in code, and keeps the SPF feature registry internally consistent.
Core Features & Use Cases
- Source triangulation and decomposition check: Gathers context from Notion docs, GitHub issues, pasted writeups, and existing feature docs, then recommends whether to extend an existing entry or create a standalone one.
- Code-grounded drafting: Maps behaviors, actors, state slots, and config inputs from the codebase so implementation claims match reality, with definition depths (coarse, technical, sketched) matched to feature maturity.
- Failure-mode catalog and cross-doc cascade: Applies a growing catalog of known risk patterns (MSE codec-change checks, multi-writer slots, API-as-feature inflation) and cascades narrow updates to related feature docs.
- Use Case: When asked to document the current depth of discontinuity handling, the Skill produces a compact entry separating implemented behavior, remaining decisions, constraints, and source pointers, then updates related registry docs.
Quick Start
Ask the assistant to document a new SPF feature or update an existing feature registry entry, providing the feature name or a description.
