update-specification

Update specification files for AI-ready consumption based on new requirements or code changes.

- Modifies existing specification documents in /spec/ directory using structured markdown with YAML front matter

- Ensures specifications are precise, unambiguous, and machine-readable through established formatting standards (headings, lists, tables, code blocks)

- Covers 11 core sections: purpose, definitions, requirements, interfaces, acceptance criteria, testing strategy, rationale, dependencies, examples, validation, and related specs

- Enforces naming convention [a-z0-9-]+.md with descriptive prefixes (schema, tool, data, infrastructure, process, architecture, design)

Update Specification

Your goal is to update the existing specification file ${file} based on new requirements or updates to any existing code.

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: [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.