create-specification

Generates structured Markdown specification files optimized for Generative AI consumption.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing technical specifications that both humans and AI systems can reliably interpret is difficult; this Skill produces a standardized, unambiguous specification document following a fixed template. ## Core Features & Use Cases - Standardized Spec Template: Generates specifications with 11 required sections including requirements, interfaces, acceptance criteria, and validation criteria. - AI-Optimized Writing Rules: Enforces precise language, defined acronyms, structured formatting, and self-contained content for machine readability. - Naming & Storage Conventions: Saves files to the /spec/ directory using the spec-[a-z0-9-]+.md convention prefixed by purpose categories like schema, tool, data, or architecture. - Use Case: Ask the AI to create a specification for a new API integration, and receive a complete Markdown spec with requirement IDs, Given-When-Then acceptance criteria, and dependency mappings. ## Quick Start Ask the AI to create a specification for your solution component, stating its purpose such as schema, tool, data, infrastructure, process, architecture, or design.

Frequently Asked Questions about create-specification

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

FAQPage Schema
How do I create a technical specification file with AI?

Invoke the skill with the specification's purpose, such as schema, tool, data, infrastructure, process, architecture, or design. The AI generates a complete Markdown spec following the standard template and saves it to the /spec/ directory.

What sections should a software specification document include?

This template requires 11 sections: Introduction, Purpose & Scope, Definitions, Requirements & Constraints, Interfaces & Data Contracts, Acceptance Criteria, Test Automation Strategy, Rationale, Dependencies, Examples & Edge Cases, and Validation Criteria.

What naming convention do specification files use?

Files are saved in the /spec/ directory and must match the pattern spec-[a-z0-9-]+.md. The name should describe the content and start with the high-level purpose such as schema, tool, data, or architecture.

How do I write acceptance criteria in a specification?

Use the Given-When-Then format with unique identifiers like AC-001. Each criterion states a context, an action, and the expected outcome, making requirements testable and verifiable.

Can the specification include specific library versions?

The Dependencies section should focus on architectural needs rather than specific package versions. Specify capability requirements like OAuth 2.0 authentication library instead of exact package versions unless they represent architectural constraints.