update-specification

Updates existing specification files into structured Markdown optimized for Generative AI consumption.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill update-specification-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-specification
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/update-specification
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill update-specification-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping technical specification documents accurate and machine-readable is difficult when requirements or code change, leading to stale docs that AI tools and developers cannot reliably parse. ## Core Features & Use Cases - Spec Modernization: Rewrites an existing specification file to follow a strict, AI-friendly Markdown template with frontmatter and numbered sections. - Standardized Structure: Enforces sections for requirements, constraints, interfaces, acceptance criteria, test strategy, dependencies, and validation criteria. - Naming Conventions: Saves output to the /spec/ directory using a [a-z0-9-]+.md naming pattern prefixed by purpose (schema, tool, data, infrastructure, process, architecture, or design). - Use Case: After refactoring an API, ask the AI to update the corresponding spec file so requirements, acceptance criteria, and data contracts reflect the new implementation. ## Quick Start Update the specification file for the authentication module based on the recent code changes and save it to the spec directory.

Frequently Asked Questions about update-specification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a technical specification document with AI?

Provide the existing specification file and describe the new requirements or code changes. The skill rewrites the document following a fixed Markdown template with frontmatter, numbered sections, and explicit requirement identifiers, then saves it to the /spec/ directory.

What makes a specification file AI-readable?

AI-readable specifications use precise unambiguous language, structured headings and tables, defined acronyms, and explicit requirement IDs like REQ-001. They avoid idioms and context-dependent references so language models can parse them reliably.

What naming convention should specification files follow?

Specification files are saved in the /spec/ directory using lowercase kebab-case matching [a-z0-9-]+.md. The name should start with the high-level purpose: schema, tool, data, infrastructure, process, architecture, or design.

What sections must a specification document include?

The template requires frontmatter metadata plus sections for purpose and scope, definitions, requirements and constraints, interfaces and data contracts, acceptance criteria, test automation strategy, rationale, dependencies, examples, validation criteria, and related specifications.

When should I not use a full specification template?

The full template is heavyweight for trivial changes or small scripts where a short README suffices. It is best suited for components with formal requirements, interfaces, and acceptance criteria that multiple stakeholders or AI tools must consume.