skills.rest
AndreaCadonna
AndreaCadonnaCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven-architecture

Define implementation-ready specifications for software architecture blocks before coding.

Updated Mar 8, 2026
Search Tags:#design#architecture#validation#spec#data model#state machine#module spec
One-click install
npx skills add https://github.com/AndreaCadonna/sbobuz-web-game-app --skill spec-driven-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-architecture
Source: https://github.com/AndreaCadonna/sbobuz-web-game-app/tree/main/skills/spec-driven-architecture
Command: npx skills add https://github.com/AndreaCadonna/sbobuz-web-game-app --skill spec-driven-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates uncertainty and ad-hoc design by forcing teams to produce a complete, reviewable architecture specification before any implementation begins. It helps surface interfaces, edge cases, data flows, and failure modes so code becomes a faithful artifact of a vetted design rather than guesswork.

Core Features & Use Cases

  • Structured Spec Template: A repeatable skeleton covering header, overview, typed data model, behavior rules, contracts, validation, reducer logic, edge cases, integration points, and resolved decisions.
  • Developer-Ready Outputs: Produces implementation-ready artifacts that a developer or agent can use to build modules independently.
  • Risk Reduction: Clarifies priorities, validation gates, and resolution order to prevent ambiguous behaviors and subtle bugs.
  • Use Cases: Designing a leaderboard module with ELO updates, specifying a notification delivery system, or drafting a matchmaking queue state machine before coding.

Quick Start

Write a complete spec for the leaderboard module that defines scope, typed data models, rating behavior, action contracts, validation rules, edge cases, and integration points.

Frequently Asked Questions about spec-driven-architecture

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

FAQPage Schema
How do I write implementation-ready software architecture specs before coding?▼

Implementation-ready software architecture specs are produced by defining typed data models, explicit behavior rules, action contracts, validation rules, and edge cases. This process eliminates ad-hoc design and ensures code becomes a faithful artifact of a vetted design rather than guesswork.

What is the best way to define a state machine specification for a software module?▼

The best way to define a state machine specification is by documenting state reducers, behavior rules, and action contracts. This structured spec template clarifies state transitions and failure modes before writing implementation code, preventing ambiguous behaviors and subtle bugs.

How do I structure API contracts and validation rules for a new service?▼

API contracts and validation rules are structured by specifying typed data models, action contracts, and validation gates within a repeatable spec skeleton. This approach surfaces interfaces and data flows so a developer can build modules independently without ambiguity.

Can I use this spec-driven approach for both frontend and backend system design?▼

Yes, this spec-driven approach applies to modules, components, services, APIs, state machines, workflows, and refactors across both frontend and backend systems. It produces developer-ready artifacts containing integration points and resolved design decisions for independent implementation.

Why should I write architecture specifications before implementation instead of during?▼

Writing architecture specifications before implementation reduces risk by clarifying priorities, validation gates, and resolution order. It surfaces interfaces, edge cases, and failure modes upfront so code becomes a faithful artifact of a vetted design rather than guesswork.

Related Skills

Explore More Software Engineering Skills→
Fr-e-dFr-e-d
157

architecture-extract

Analyze project directory structures to generate architectural summaries.

Community
Basic
hachejhachej
45

prototype

Create throwaway terminal and UI prototypes to validate software design decisions.

Community
Intermediate
t-stringst-strings

Global Validation

Enforce centralized validation standards across repository code and CI pipelines.

Official
Basic
oiagorodriguesoiagorodrigues

mermaid-studio

Create, validate, and render Mermaid diagrams to SVG, PNG, or ASCII.

Community
Advanced