spec-creator

name

spec-creator

description

Create production-grade SPEC.md files — portable implementation contracts that any AI coding agent can build from without follow-up questions. Use this skill whenever the user wants to write a spec, specification, technical spec, implementation contract, SPEC.md, or service specification for any software task. Also trigger when the user says "spec out", "write a spec for", "create a spec", "define the contract for", or describes a system they want built and needs a thorough specification before implementation. This skill works for backend services, full-stack apps, CLI tools, SDKs, developer tools, and any domain. It produces specs at the level of a principal-engineer-authored portable implementation contract — not a PRD, not an HLD, but the artifact that sits between architecture and code.

Spec Creator

Create implementation-grade SPEC.md files through structured brainstorming, then drafting, then self-review. The output is a single monolithic Markdown specification that an AI coding agent can implement without asking clarifying questions.

Quality Bar

The target quality level is a portable implementation contract — the kind of document a principal engineer writes so any competent engineer (or AI agent) in any language can build a conforming implementation. Read references/quality-bar.md for the full quality rubric before starting any spec.

Key quality markers (internalize these, don't just check them off):

• Every entity field has a type, default value (if applicable), and validation rule
• Every error has a named category and explicit recovery behavior
• Every state transition has explicit triggers and outcomes
• Every boundary says what is in scope AND what is out of scope
• Reference algorithms are provided in language-agnostic pseudocode for complex logic
• Configuration has a cheat-sheet section for quick agent consumption
• The test/validation matrix maps back to spec sections
• Forward compatibility is addressed (e.g., "unknown keys should be ignored")