create-specification

Create machine-readable Markdown specification files with front matter and structured sections.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill create-specification-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-specification
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/create-specification
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill create-specification-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many teams struggle to produce clear, unambiguous, and machine-consumable specifications that capture requirements, constraints, interfaces, and acceptance criteria in a consistent format suitable for Generative AI consumption and downstream automation.

Core Features & Use Cases

  • Structured AI-Ready Output: Produces a Markdown specification with front matter and clearly separated sections for purpose, definitions, requirements, interfaces, acceptance criteria, testing strategy, dependencies, examples, and validation.
  • Consistency & Machine-Readability: Enforces naming conventions, section templates, and a file naming pattern to support automated discovery, parsing, and versioning.
  • Use Cases: Creating API/data schemas, architecture or infrastructure specs, testable acceptance criteria for feature development, and handoffs for engineering or compliance reviews.

Quick Start

Draft a concise, AI-optimized specification named spec-architecture-payment-gateway that defines scope, requirements, interfaces, data contracts, acceptance criteria, test strategy, dependencies, and example edge cases.

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 files for software requirements?

AI-ready specification files are produced as structured Markdown with front matter, requirements, interfaces, acceptance criteria, and validation sections. This format ensures unambiguous machine consumption for downstream Generative AI automation.

How do I create machine-readable acceptance criteria and data contracts for feature development?

Creating machine-readable acceptance criteria and data contracts involves defining them within structured Markdown sections. The output enforces naming conventions and templates to support automated discovery, parsing, and versioning.

Can I use this to write infrastructure and architecture specifications?

Yes, you can write infrastructure and architecture specifications. The tool applies to software, data, architecture, infrastructure, process, design, and tool specifications for AI consumption in development and integration scenarios.

What is the best way to structure requirements and interfaces for automated parsing?

The best way to structure requirements for automated parsing is using consistent Markdown with front matter, clear section templates, and enforced file naming patterns. This standardizes data for downstream engineering and compliance reviews.

What format do specification files need to be in for AI consumption?

Specification files for AI consumption must be machine-readable, well-structured Markdown. They require front matter and separated sections for purpose, definitions, requirements, interfaces, testing strategy, dependencies, and validation.

Does this specification generator support test strategy and validation criteria sections?

Yes, the specification generator supports test strategy and validation criteria sections. It produces well-structured Markdown containing dedicated sections for testing strategy, examples, and validation alongside requirements and dependencies.