skills.rest
sofer
soferCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec

Generate precise specifications with contracts, schemas, and acceptance criteria for a user story.

Updated Aug 23, 2026
Search Tags:#specification#edge-cases#contracts#acceptance-criteria#data-schemas#behaviours
One-click install
npx skills add https://github.com/sofer/.agents --skill spec-sofer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/sofer/.agents/tree/main/skills/spec
Command: npx skills add https://github.com/sofer/.agents --skill spec-sofer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams generate clear, testable specifications for a single user story, ensuring alignment before design and development.

Core Features & Use Cases

  • Contract and schema definitions to capture interfaces and data structures.
  • Behaviour-driven scenarios to map acceptance criteria to testable outcomes.
  • Edge-case handling and open-question recording to manage ambiguity and risk.

Quick Start

Generate a complete specification for a selected story, including contracts, data schemas, and behaviours.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I write testable specifications for a user story?▼

To write testable specifications for a user story, define precise contracts, data schemas, and behaviours. This ensures alignment before design and development by mapping acceptance criteria to testable outcomes.

What is the best way to capture edge cases in acceptance criteria?▼

Capturing edge cases in acceptance criteria requires behavior-driven scenarios and open-question recording. This manages ambiguity and risk by explicitly defining how the system handles unexpected inputs.

How do I define data schemas and contracts before development?▼

You define data schemas and contracts by generating a complete specification for a selected story. This process captures required interfaces and data structures to ensure production-ready alignment.

Can I map user story behaviours to testable outcomes?▼

Yes, you can map user story behaviours to testable outcomes using behavior-driven scenarios. This translates acceptance criteria into concrete tests, ensuring the specification remains precise and verifiable.

When do I need to generate a production-ready spec for a backlog story?▼

You need to generate a production-ready spec when a backlog story is selected for implementation. This defines interfaces, data structures, and edge cases to satisfy all acceptance criteria before coding begins.

Related Skills

Explore More Product & Management Skills→
ThanabordeeNThanabordeeN

product-backlog-agent

Convert user requirements into backlog, user stories, and sprint plan files.

Community
Advanced
AmiraultAmirault
1

implement

Executes validated software specifications with automated build and test cycles.

Community
Advanced
interactive-incinteractive-inc
1

backlog

Record, update, and plan tasks within a project backlog.

Official
Intermediate
nodatallnodatall
2

clarifier

Coach guided revision of rough writing while preserving the original voice.

Community
Intermediate