create-specification

Generate Markdown specification documents with YAML frontmatter in the spec/ directory.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/javiertelioz/my-personal-marketplace --skill create-specification-javiertelioz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-specification
Source: https://github.com/javiertelioz/my-personal-marketplace/tree/main/plugins/create-specification/skills/create-specification
Command: npx skills add https://github.com/javiertelioz/my-personal-marketplace --skill create-specification-javiertelioz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates clear, unambiguous AI-ready specifications that define requirements, constraints, and interfaces for a solution, reducing ambiguity and rework in downstream development.

Core Features & Use Cases

  • Structured frontmatter and Markdown body that captures scope, definitions, interfaces, and acceptance criteria.
  • Clear guidance on writing machine-readable specifications with explicit sections, definitions, and examples.
  • Use Case: A product team generates a specification for a new feature to align engineering, design, and QA expectations.

Quick Start

Create a new specification document in the spec/ directory named spec-design.md for the given solution.

Frequently Asked Questions about create-specification

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

FAQPage Schema
How do I generate AI-ready specification documents for software requirements?

To generate AI-ready specification documents, use a structured Markdown template with YAML frontmatter that defines purpose, scope, requirements, data contracts, and acceptance criteria to reduce ambiguity in downstream development.

What should be included in an AI-ready specification for development and reviews?

An AI-ready specification should include sections for purpose, scope, definitions, requirements, data contracts, and acceptance criteria. This structure captures interfaces and constraints to guide development and reviews.

How do I structure a specification document to reduce ambiguity for engineering and QA teams?

Structure a specification document with structured frontmatter and a Markdown body that captures scope, definitions, interfaces, and acceptance criteria to align engineering, design, and QA expectations.

Can I use a standard specification template for defining requirements and interfaces?

Yes, you can apply a standard specification template with explicit sections, definitions, and examples to write machine-readable specifications that clearly define requirements and interfaces for a given solution.

What's the best way to write machine-readable specifications with clear definitions and examples?

The best way to write machine-readable specifications is to apply a standard template with structured Markdown and YAML frontmatter, using explicit sections, definitions, and examples to guide development and reviews.

Do I need to follow a specific naming convention when saving specification files in the spec directory?

Yes, you need to save the generated specification document in Markdown under the spec/ directory following the naming convention spec-design.md to maintain consistent specification files.