Skip to content

SDS β€” Spec-Defined Software (Requirement Delivery Version)

Welcome to the future of software engineering.

Spec-Defined Software (SDS) is the transition of requirement delivery from manual coding to precise, AI-collaborative specification-defining. In this paradigm, a business requirement's complete behavioral and business identity is codified in its spec.md (the "What") and mapped to its technical realization in design.md (the "How").

The physical code, database migrations, tests, and deployment configurations are treated as logical derivatives that can be automatically synthesized, verified, and self-healed by advanced AI engines.


πŸš€ The SDS Philosophy: Code is Compile Target

Always treat the Specification as the absolute source of truth for the entire requirement delivery process. Prioritize the completeness and clarity of the Specification over immediate coding.

  [ User Scenario ] βž” [ Accepted Spec & Design ] βž” [ Implementation ] βž” [ Verification ] βž” [ Requirement Delivery ]

The code is merely a compiled artifact of the delivered requirement. By keeping our edits highly focused on the Spec-first delivery model, we map every change back to an Acceptance Criterion (AC) in the Spec, achieving zero-drift development.


πŸ› οΈ The SDS Core-Centric Lifecycle Suite

To move away from passive "linting" and support the entire software delivery pipeline, SDS orchestrates multiple specialized agent skills:

  1. sds-ideator (Demand Phase): A Socratic Brainstorming Skill that guides developers in refining fuzzy user requirements into crisp, Gherkin-style Acceptance Criteria.
  2. sds-architect (Design Phase): Translates product spec requirements into formal API contracts, DB schema migrations, and technical patterns.
  3. sds-coder (Implementation Phase): Spawns isolated coding subagents to implement physical features and unit tests, automatically maintaining @sds-trace coverage.
  4. sds-qa (Verification Phase): πŸ§ͺ The Quality Gatekeeper. Automatically synthesizes test suites from spec.md ACs and connects them back to user-journey.md (User Story) flows to achieve complete requirement closure.
  5. sds-ops (Delivery Phase): Executes atomic deployments using symlinked environments, manages database migration ledgers, and runs regression smoke checks.

πŸ“¦ Instant Quickstart

Get started with the SDS CLI in seconds:

1. Installation

Install the CLI tool globally using our one-line installer:

curl -fsSL https://raw.githubusercontent.com/flingfox63/spec-defined-software/main/install.sh | sh

2. Initialization

Run the initialization scaffold in the root of your project directory:

sds init
This generates the .sds.harness.yaml config and sets up the standard specs/ directory layout.

3. Run Verification Checks

Verify your repository structure, code annotations, and check for spec-to-code drift:

sds check

πŸ—ΊοΈ Ecosystem Roadmap

The SDS platform is evolving from a baseline linting tool into a fully automated, E2E AI-collaborative software delivery operating system. Below is our development timeline and milestones:

Milestone / Module Target Status Core Deliverables & Capabilities
sds-core
(The Guardrail)
Shipped 🟒 Released β€’ Statically verifies directory layouts and Frontmatter states.
β€’ Integrates pre-commit Git hooks and global installers.
β€’ Exposes standard stdio Model Context Protocol (MCP) server.
sds-ideator
(Socratic PM)
Q3 2026 🟑 In Progress β€’ Socratic alignment prompt suites to refine loose ideas into BDD Gherkin ACs.
β€’ Synthesizes and drafts initial spec.md files in specs_review/.
sds-architect
(Lead Engineer)
Q3 2026 🟑 In Progress β€’ Compiles accepted product specs into concrete technical schemas.
β€’ Auto-generates TypeScript/Go API contracts, database migrations, and design.md.
sds-coder
(Autonomous Synthesizer)
Q4 2026 πŸ”΅ Planned β€’ Subagent-driven code writer implementing functions directly from specs.
β€’ Automatically inserts @sds-trace anchors and self-heals compiler/drift errors.
sds-qa
(BDD Test Compiler)
Q4 2026 πŸ”΅ Planned β€’ Synthesizes runnable integration, unit, and E2E test scripts from ACs.
β€’ Mandates a quality gate verification prior to deployment triggering.
sds-ops
(Atomic Release)
Q1 2027 πŸ”΅ Planned β€’ Capistrano-style atomic releases with symbolic-link switching.
β€’ Automated virtualenv isolation and remote passwordless rollback controls.

πŸ’– Heritage & Inspiration

Spec-Defined Software (SDS) is proud of its roots and is heavily inspired by and evolved from GitHub's spec-kit methodology. We extend the original spec-kit patterns by introducing automated zero-drift linting, multi-agent LLM orchestration safety gates, and physical bidirectional traceability (@sds-trace) engineered specifically for the AI native era.


[!NOTE] SDS is fully compatible with modern Multi-Agent orchestration frameworks and MCP protocols, giving your AI coding assistant native tools to read, update, and test specs.