要点
Generate structured, AI-optimized specification documents with standardized templates and machine-readable formatting.
- Creates specification files in
/spec/directory following naming conventionspec-[purpose]-[type].mdwith YAML front matter for metadata - Enforces structured markdown with 11 standard sections covering purpose, requirements, interfaces, acceptance criteria, and validation
- Includes explicit guidelines for unambiguous language, acronym definitions, and self-contained documentation designed for AI consumption
- Supports multiple specification types: schema, tool, data, infrastructure, process, architecture, and design
SKILL.md
Create Specification
Your goal is to create a new specification file for ${input:SpecPurpose}.
The specification file must define the requirements, constraints, and interfaces for the solution components in a manner that is clear, unambiguous, and structured for effective use by Generative AIs. Follow established documentation standards and ensure the content is machine-readable and self-contained.
Best Practices for AI-Ready Specifications
- Use precise, explicit, and unambiguous language.
- Clearly distinguish between requirements, constraints, and recommendations.
- Use structured formatting (headings, lists, tables) for easy parsing.
- Avoid idioms, metaphors, or context-dependent references.
- Define all acronyms and domain-specific terms.
- Include examples and edge cases where applicable.
- Ensure the document is self-contained and does not rely on external context.
The specification should be saved in the /spec/ directory and named according to the following convention: spec-[a-z0-9-]+.md, where the name should be descriptive of the specification's content and starting with the highlevel purpose, which is one of [schema, tool, data, infrastructure, process, architecture, or design].
The specification file must be formatted in well formed Markdown.