Padroniza documentação existente no formato canônico Spec-Driven. Remove duplicação e melhora rastreabilidade.
66%
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-normalizer/SKILL.mdNormalize, restructure, and clean documentation into the canonical spec format:
This skill does NOT add new requirements. It reorganizes and clarifies existing information.
List docs discovered and categorize: Context, Requirements, Design, Decisions, Runbooks.
Move/merge content into: spec/00-context/, spec/10-requirements/, spec/20-design/, spec/90-decisions/, spec/99-meta/.
If content is duplicated: keep a single source of truth, add links from other places.
Add links: PRD goals ↔ FRs; FRs ↔ Acceptance criteria; FRs ↔ Design sections (API/data model).
Check for: Vague terms ("fast", "secure", "user-friendly"); Missing definitions (glossary); Missing unknowns; Overly long paragraphs.
spec/00-context/ | 10-requirements/ | 20-design/ | 30-features/ | 90-decisions/ | 99-meta/
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.