Dictionary (New Word): Spec-Driven Development (SDD) #258
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jargons-dev
bot
added
💻via-jargons-editor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
babblebey
approved these changes
Dec 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Word
Spec-Driven Development (SDD)
Meaning/Definition
Spec Driven Development (SDD) is a software development approach where detailed specifications or requirements are created before writing the actual code. These specifications guide the design, implementation, and testing of the software to ensure it meets the desired functionality.
This method emphasizes clear, upfront documentation of what the software should do, helping teams align on expectations and reduce misunderstandings. It often involves writing formal or semi-formal documents that describe features, user interactions, and system behavior in detail.
Example: In Spec Driven Development, a team might write a specification stating, "The login feature must allow users to enter a username and password, validate credentials, and redirect to the dashboard upon success," before any coding begins.