create-specification

Creates structured Markdown specification files optimized for Generative AI consumption.

37|4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill create-specification-jmrplens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-specification
Source: https://github.com/jmrplens/gitlab-mcp-server/tree/main/.github/skills/create-specification
Command: npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill create-specification-jmrplens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing technical specifications that both humans and AI systems can reliably interpret is difficult; this Skill generates a standardized, machine-readable specification document with a fixed section template and naming convention. ## Core Features & Use Cases - Standardized Template: Produces specifications with 11 required sections covering purpose, definitions, requirements, interfaces, acceptance criteria, test strategy, dependencies, and validation criteria. - AI-Ready Formatting: Enforces unambiguous language, defined acronyms, structured headings, and self-contained content so Generative AI tools can parse the spec reliably. - Naming Convention: Saves files to the spec/ directory using the pattern spec-[a-z0-9-]+.md, prefixed by purpose categories such as schema, tool, data, infrastructure, process, architecture, or design. - Use Case: When starting a new feature, ask the AI to create a specification for the authentication module, and receive a complete spec file with requirement IDs, Given-When-Then acceptance criteria, and dependency listings. ## Quick Start Ask the AI to create a specification for your intended purpose, for example: create a specification for the new API rate limiting component.

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 for AI consumption?

Invoke the skill with the specification's purpose, and it generates a Markdown file following a fixed template with sections for requirements, interfaces, acceptance criteria, and dependencies. The file is saved in the spec/ directory using the spec-[a-z0-9-]+.md naming convention.

What sections should a software specification document include?

This template includes 11 sections: Purpose & Scope, Definitions, Requirements & Constraints, Interfaces & Data Contracts, Acceptance Criteria, Test Automation Strategy, Rationale, Dependencies, Examples, Validation Criteria, and Related Specifications.

What naming convention does the specification file use?

Files are named spec-[a-z0-9-]+.md and stored in the spec/ directory. The name should start with the high-level purpose, one of schema, tool, data, infrastructure, process, architecture, or design.

How are acceptance criteria formatted in the specification?

Acceptance criteria use identifiers like AC-001 and follow the Given-When-Then format where appropriate, or declarative statements such as 'The system shall [behavior] when [condition]' for testable requirements.

Should the specification list specific package versions as dependencies?

No. The Dependencies section focuses on architectural and business dependencies rather than implementations. Specify capability needs like 'OAuth 2.0 authentication library' instead of exact package versions unless they represent architectural constraints.