create-specification

To generate machine-readable software specification documents with frontmatter, this Skill creates architecture-ready specs in the /spec/ directory using the spec-[a-z0-9-]+.md naming convention, enforcing a schema for version, domain, triggers, role, and scope. It ensures consistent delivery and automated discovery across teams.

The best way to define requirements, interfaces, and data contracts for AI-assisted development is using template-driven specifications. This Skill produces structured sections for Definitions, Requirements, Interfaces & Data Contracts, and Acceptance Criteria to clearly establish constraints and guide consistent solution delivery.

Creating precise architecture specifications that support versioning and traceability involves applying a structured frontmatter schema and mandated naming conventions. This Skill outputs machine-ready documents to the /spec/ directory, enabling automated discovery and tracking across development workflows.

Yes, you can use this specification template for non-functional requirements and acceptance criteria. The Skill's template-driven content explicitly includes dedicated sections for Acceptance Criteria and non-functional considerations alongside Definitions, Requirements, and Interfaces.

Yes, this specification approach enforces a strict file naming convention and directory structure. It saves all generated markdown documents under the /spec/ directory using the designated spec-[a-z0-9-]+.md pattern to enable automated discovery, versioning, and traceability.

An architecture-ready specification for software solutions includes structured frontmatter followed by Introduction, Definitions, Requirements, Interfaces & Data Contracts, and Acceptance Criteria sections. It also incorporates guidelines for formatting, versioning, traceability, and non-functional considerations.