skills.rest
vtex
vtexOFFICIAL
Explore all skills by this author →
Website𝕏@VTEXcommerceGitHub

specification

Generate a Spec Driven Development markdown document with Business Context, Arch Decisions, and Technical Contract.

60|12|Updated Aug 1, 2013
Search Tags:#architecture#documentation#github#requirements#spec#sd d#technical contract
One-click install
npx skills add https://github.com/vtex/front.phone --skill specification-vtex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specification
Source: https://github.com/vtex/front.phone/tree/main/.agents/skills/specification
Command: npx skills add https://github.com/vtex/front.phone --skill specification-vtex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you avoid vague requirements by producing a complete Spec Driven Development (SDD) document that aligns business intent, architecture choices, and the technical contract needed to start implementation.

Core Features & Use Cases

  • Generates a full SDD with three required sections: Business Context, Arch Decisions, and Technical Contract.
  • Supports single-pass or interactive discovery depending on how much information is available to write the spec correctly.
  • Writes the spec to the repo in the specs/<feature-name>.md path using the project template for consistent structure and acceptance criteria.

Quick Start

Ask the agent to create a specification for a feature, and it will generate the SDD file under specs/<feature-name>.md.

Frequently Asked Questions about specification

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

FAQPage Schema
How do I turn feature ideas into implementable technical specs?▼

To turn feature ideas into implementable technical specs, you generate an SDD markdown document capturing Business Context, Arch Decisions, and a Technical Contract. This aligns business intent and architecture choices before implementation begins.

What is Spec Driven Development and when do I need it?▼

Spec Driven Development is a process that produces a markdown document capturing Business Context, Arch Decisions, and a Technical Contract. You need it when vague requirements risk misaligning business intent and technical implementation.

How do I write a technical contract with actionable acceptance criteria?▼

You write a technical contract with actionable acceptance criteria by applying a standardized SDD template. This enforces complete sections for architecture decisions and technical requirements, resulting in a structured markdown file.

Can I create a specification using single-pass generation instead of interactive discovery?▼

Yes, you can create a specification using single-pass generation. The SDD process supports single-pass output when sufficient information is available, or interactive discovery to gather missing details for the technical contract.

How do I avoid duplicating features when gathering repository context for a new spec?▼

To avoid duplicating features when gathering repository context, the spec generation process analyzes existing repo structure. It writes the new SDD to specs/<feature-name>.md, ensuring new technical contracts build on existing architecture decisions.

Related Skills

Explore More Software Engineering Skills→
kevindreekevindree

idea-refine

Refine raw ideas into actionable plans with structured thinking and markdown one-pagers.

Community
Advanced
0xHoneyJar0xHoneyJar
3

Sprint Planner

Convert PRD and SDD documents into a sprint plan with deliverables and acceptance criteria.

Official
Advanced
Akiyama-samaAkiyama-sama

sdd-close

Automates verification, archiving, and review-gating of completed SDD changes in a repository.

Community
Intermediate
eburairueburairu
1

sdd-requirements

Generate structured requirements.md files from feature concepts and steering documents.

Community
Intermediate