spec-driven-dev

The skill footprint is coherent with its stated purpose: it defines a disciplined, phase-gated, spec-driven development workflow with per-spec scoping, local file-based artifacts, and explicit approvals. There are no evident security, credential, or supply-chain risks based on the provided material; the workflow remains within developer tooling boundaries and does not introduce external dependencies or data flows beyond local document management and version control.