service-create

To create standardized documentation for a new service, invoke the service-create command with the service name to generate a complete 10-section SSOT-compliant markdown skeleton at specs/docs/{svc}.md.

An SSOT-compliant service specification is a standardized per-service markdown file containing a 10-section structure and required frontmatter like name and description, serving as the single source of truth for the service.

You need to generate a per-service documentation file when a new service appears in your project or when an existing service lacks the required 10-section SSOT-compliant documentation.

Yes, the service documentation template validates and enforces required frontmatter fields, specifically ensuring that both the name and description attributes are present before applying the project standard templates.

The best way to document an undocumented service is to apply an automated SSOT workflow that validates required frontmatter and generates a complete 10-section standardized document skeleton.

Service specification generation fails without frontmatter because the SSOT workflow validation enforces required name and description attributes to ensure standard structure alignment before creating the document.