skills.rest
kscius
ksciusCOMMUNITY
Explore all skills by this author →
Website𝕏@ksciusGitHub

spec-driven-development

Create machine-readable technical specifications with signatures, invariants, and edge cases.

2|Updated Apr 3, 2026
Search Tags:#planning#testing#documentation#specification#edge-cases#contracts
One-click install
npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill spec-driven-development-kscius
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/spec-driven-development
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill spec-driven-development-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create machine-readable technical specs before implementing non-trivial features, APIs, or refactors. Use before BUILD phase when PLAN is STANDARD/COMPLEX and precise typed contracts, behavioral invariants, and example pairs are needed for validation. Triggers on "write a spec", "spec-first", "define the contract".

Core Features & Use Cases

  • Stepwise method to craft typed function signatures, invariants, pre/postconditions, edge cases, and executable examples.
  • Produces a complete spec document ready for review and implementation, ensuring alignment between planners, reviewers, and engineers.
  • Use during PLAN/BUILD handoffs to lock down contracts before coding.

Quick Start

Describe the subject, boundaries, and goals of the feature, then request a complete spec following Steps 2–7.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I write a technical specification before implementing a complex API?▼

A machine-readable technical specification includes exact signatures, behavioral invariants, pre/postconditions, edge cases, executable examples, out-of-scope boundaries, and acceptance criteria to ensure alignment between planners and engineers.

When do I need to use spec-first development for a refactor?▼

To create a specification for a non-trivial feature, describe the subject, boundaries, and goals of the feature, then request a complete spec document following the stepwise method to craft typed signatures and acceptance criteria.

What is the best way to define contracts and edge cases for a new feature?▼

Using a specification-first approach for non-trivial features distinguishes itself by producing a complete, machine-readable spec document with exact signatures and acceptance criteria, ensuring alignment between planners, reviewers, and engineers before coding.

Does spec-first planning work for standard and complex software engineering tasks?▼

Yes, spec-first planning works for standard and complex software engineering tasks, applying to planning and validation phases when exact signatures, invariants, edge cases, and executable examples are needed for validation.

Related Skills

Explore More Software Engineering Skills→
GulajavaMinistudioGulajavaMinistudio
55

planner-architect

Convert technical specifications into machine-readable implementation plans.

Community
Advanced
chughtapanchughtapan

spec

Convert user intent into a formal spec document with goals and acceptance criteria.

Community
Intermediate
pyzepyze

bdd-scenarios

Convert specification examples into executable Given/When/Then scenarios using clojure.test.

Official
Basic
kensauruskensaurus
8

spec-writing

Create structured specs with goals, constraints, and acceptance criteria.

Community
Advanced