Processo universal e repetível para criar especificações a partir de qualquer input (texto, docs, código). Usado em Plan mode.
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/workflow/spec-driven-core/SKILL.mdProvide a universal, repeatable process to create specifications from any input: text, documents, code, diagrams or conversations. This skill is educational and operational.
Do NOT jump to implementation. Do NOT write production code unless explicitly requested after specs are approved.
Answer explicitly: What exists today? Why does this exist? Who uses it? What problem does it solve?
Convert intent into requirements. Rules: each requirement must be observable; no implementation details; no UI assumptions.
For each requirement: define success, failure, edge cases. Use Given/When/Then.
Define limits and obligations: performance, security, availability, compliance, observability. Each must include verification method.
Translate requirements into structure. Rules: design serves requirements; trade-offs must be explicit; decisions must be logged (ADRs).
Verify traceability, completeness, no hidden assumptions, no vague language.
Never skip a layer.
spec/ (or docs/specs/)
00-context/
10-requirements/
20-design/
30-features/
90-decisions/
99-meta/A spec is complete when:
f84a77a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.