Agent skill spec-driven-development has no path for creating a spec

Bug Description .agents/skills/spec-driven-development/SKILL.md is read by coding agents working in this repo. It covers finding a spec, following it during implementation, and verifying that code and spec have not drifted — but it has no path for creating one. Step 3 of "Before Starting Work" reads: > If no spec exists and the task is non-trivial (new module, new API, > architectural change), ask the user whether to create one first. and stops there. The skill has a "Spec File Conventions" section, but it describes the finished file (where it lives, keep it concise, use Implementation TODO checkboxes) — not how to get to one. If the user sayss for resolving the ambiguity in the request first, no set of sections to fill in, and no criterion for when a spec is not worth writing. Each or quietly skips the spec. The effect is visible in the repo: .agents/specs/ does not exist on master. No spec has ever been written under this process, so the ski ("Rea…