create-specification

Creates structured Markdown specification files optimized for Generative AI consumption.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill create-specification-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-specification
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/core/create-specification
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill create-specification-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing specifications that both humans and AI systems can reliably interpret is difficult; this Skill produces a standardized, machine-readable specification document with unambiguous requirements, constraints, and acceptance criteria. ## Core Features & Use Cases - Standardized Template: Generates specifications with 11 fixed sections covering purpose, definitions, requirements, interfaces, acceptance criteria, test strategy, dependencies, and validation. - AI-Ready Formatting: Enforces precise language, structured headings, defined acronyms, and self-contained content so Generative AI tools can parse the spec without external context. - Naming & Storage Convention: Saves files to the /spec/ directory using the spec-[a-z0-9-]+.md pattern prefixed by purpose categories like schema, tool, data, infrastructure, process, architecture, or design. - Use Case: When starting a new service, ask the agent to create an architecture specification and receive a complete Markdown document with REQ/CON/GUD identifiers and Given-When-Then acceptance criteria. ## Quick Start Create a specification for the new authentication service covering its requirements, interfaces, and acceptance criteria.

Frequently Asked Questions about create-specification

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

FAQPage Schema
How do I write a specification document for AI consumption?

Use precise, unambiguous language with structured headings, lists, and tables. Define all acronyms, distinguish requirements from constraints and recommendations, and keep the document self-contained so AI tools can parse it without external context.

What sections should a technical specification include?

This template uses 11 sections: introduction, purpose and scope, definitions, requirements and constraints, interfaces and data contracts, acceptance criteria, test automation strategy, rationale, dependencies, examples, and validation criteria.

How should specification files be named and organized?

Save files in the /spec/ directory using the pattern spec-[a-z0-9-]+.md. The name should start with the high-level purpose, one of schema, tool, data, infrastructure, process, architecture, or design.

How do I write testable 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 an expected outcome, making requirements directly verifiable by tests.

Should a specification list exact package versions as dependencies?

No. The dependencies section focuses on architectural and business needs, such as an OAuth 2.0 authentication library, rather than specific package versions, unless a version represents a genuine architectural constraint.