writing-specs

To write SSOT software specifications, use a structured template enforcing frontmatter presence, concise overviews, acceptance criteria, error handling notes, and dependencies within the specs/ directory to resolve cross-team alignment issues.

SSOT standards require a software spec to include frontmatter (name, description), a concise overview, acceptance criteria, error handling notes, dependencies, and used-by mappings to maintain a single source of truth.

Generate acceptance criteria and dependency mappings for a new component spec by applying an SSOT-aligned template that scaffolds these specific sections, ensuring clear relationships and terminology across the project's documentation.

You need SSOT-aligned specification templates when defining new components or updating existing documentation, ensuring that frontmatter, dependencies, and acceptance criteria remain consistent and aligned across all project teams.

You can review and update existing technical specifications to enforce SSOT principles by checking for required frontmatter, concise overviews, acceptance criteria, and used-by mappings within the specs/ directory structure.