Software Development
Spec
Turn a vague feature or product idea into an agreed, persisted specification through relentless structured questioning. Never assumes — every gap, ambiguity, or "probably" becomes a question to the developer, and the spec cannot be approved while open questions remain. Produces docs/specs/<NNN>-<slug>.md with acceptance criteria that /plan, /scaffold, and /tdd consume. Use when: "spec", "write a spec", "spec this out", "requirements", "PRD", "acceptance criteria", "define the feature", "user stories", "what should we build", or before planning any feature too big to describe in one sentence.
- Publisher / source
- codewithmukesh/dotnet-claude-kit (found on skills.sh)
- Upstream record
- codewithmukesh/dotnet-claude-kit
- Version
- Version 3
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-03
- Content fingerprint
089b0482ed2235507db1d23818abe3fc8ad69c60c0d9f1198eba677b30b8682a