What problem does it solve? Writing a spec.md that is consistent, scoped correctly, and free of contradictions with authoritative domain documentation is hard; this Skill standardizes the structure, sections, and divergence-handling rules for every work unit. ## Core Features & Use Cases - Standardized spec structure: Defines the required sections (Overview, Domain, Scope, Domain boundary, User stories, Acceptance criteria, Dependencies, Risks) and the .agents/specs/<NNN>-<slug>/ folder convention. - Divergence handling: Establishes a three-case protocol for conflicts between authoritative documentation, code, and requirements, escalating unresolved contradictions as gaps instead of deciding silently. - Scope defense: Separates product-language Scope from technical-artifact Domain boundary, and defines rules for cross-cutting specs spanning multiple domains. - Use Case: When starting a new feature unit, ask the AI to generate a spec.md that derives acceptance criteria from the domain skill documentation, keeps the boundary limited to the delta, and records open questions as gaps. ## Quick Start Ask the AI to write the spec.md for a new work unit following the spec-authoring standard, deriving acceptance criteria from the linked domain documentation.
