What problem does it solve? Feature specifications often lack traceable test coverage: requirements exist in PRDs, but there is no structured chain linking them through design allocations to concrete scenarios and executable tests. This Skill authors and reviews the Testing section of Insight FEATURE documents so every applicable FR/NFR has a scenario, a quality vector, a suite, and a linked test. ## Core Features & Use Cases - Requirement-to-test traceability: Builds the chain PRD FR/NFR → DESIGN allocation → FEATURE requirements → scenario → test, preserving canonical feature IDs and stable scenario numbers. - Vector and suite mapping: Assigns each scenario one of five quality vectors (Efficiency, Reliability, Performance, Security, Versatility) and the cheapest adequate test suite, from rust-unit and fe-unit up to stand-api, stand-ui, or observed telemetry. - Coverage gap review: Uses scripts/counts.sh to take repo-wide denominators (connectors, catalog metrics, dbt models, stand tests) that fail loudly as MOVED rather than reporting a misleading zero. - Use Case: When adding a Testing section to a new FEATURE for an ingestion connector, the Skill resolves inherited NFRs, drafts numbered scenarios with requirement citations, and links each implemented test back to its scenario. ## Quick Start Ask the assistant to write or review the Testing section of a FEATURE document, tracing its PRD requirements to vector-attributed scenarios and executable tests.
