Dëse Browser gëtt net méi ënnerstëtzt.
Upgrat op Microsoft Edge fir vun de Virdeeler vun leschten Eegeschaften, Sécherheetsupdaten, an techneschem Support ze profitéieren.
What is the primary characteristic that distinguishes spec-driven development (SDD) from traditional development approaches?
Code is treated as the ultimate source of truth, and specifications serve as supporting documentation.
Specifications become the primary artifact that drives implementation, and code becomes an expression of those specifications.
Developers write code first and then create specifications to document what was built.
What happens to specifications in spec-driven development (SDD) when requirements change?
Specifications are treated as static documents that rarely need updates once created.
Specifications are discarded and new ones are created from scratch.
Specifications are updated, and affected implementation plans and code can be regenerated accordingly.
What are the four phases of the spec-driven development (SDD) workflow?
Research, Design, Develop, and Deploy.
Specify, Plan, Tasks, and Implement.
Requirements, Architecture, Coding, and Testing.
What distinguishes spec-driven development (SDD) outputs as 'living artifacts' compared to traditional documentation?
Living artifacts are stored in version control systems.
Living artifacts can evolve as new information emerges, with changes propagating through plan, tasks, and code.
Living artifacts are automatically generated without human input.
How does spec-driven development (SDD) complement Agile methodologies?
SDD replaces Agile practices entirely with a more structured approach.
SDD can operate within Scrum by treating each user story with a micro-cycle of specify, plan, tasks, and implement.
SDD requires comprehensive upfront documentation that conflicts with Agile values.
When comparing spec-driven development (SDD) to Test-Driven Development (TDD), what is a key difference in their approach?
TDD operates at the unit test level, while SDD works at a higher requirements level to describe complete features.
TDD and SDD are mutually exclusive approaches that can't be used together.
SDD produces automated tests while TDD produces specifications.
In the Specify phase of spec-driven development (SDD), what does a well-structured specification include?
Only a high-level summary of the feature with implementation details.
Summary, user stories, acceptance criteria, functional requirements, nonfunctional requirements, and edge cases.
Architecture diagrams and technology stack decisions.
What is the purpose of the Plan phase in the spec-driven development (SDD) workflow?
To define what the software should do and capture user needs.
To determine how to build what the spec describes, including architecture decisions and technology choices.
To break down work into actionable development tasks.
What is GitHub Spec Kit?
A proprietary AI model developed by GitHub for code generation.
An open-source toolkit that facilitates spec-driven development by integrating with AI coding assistants.
A Visual Studio Code extension that replaces GitHub Copilot.
How does GitHub Spec Kit address the challenge of maintaining context across AI chat sessions?
By storing specifications, plans, and tasks as Markdown files in your repository.
By replacing the AI's memory with a cloud-based storage system.
By limiting AI interactions to a single continuous session.
What is required to install GitHub Spec Kit's specify CLI tool?
Only Visual Studio Code with the GitHub Copilot extension.
Python 3.11 or later, Git, and the uv tool for package management.
A paid enterprise license from GitHub.
Which AI coding assistants does GitHub Spec Kit support?
Only GitHub Copilot in Visual Studio Code.
Multiple agents including GitHub Copilot, Claude Code, Cursor, Windsurf, and Amazon Q Developer.
Only command-line AI tools, not IDE-integrated assistants.
What is the purpose of the constitution.md file generated by the /speckit.constitution command?
To store the source code for the application's core functionality.
To define project-wide principles, constraints, and non-negotiable requirements that ensure consistency.
To list all the tasks required for implementing a feature.
What is the recommended sequence for using GitHub Spec Kit commands in a greenfield project?
Run commands in any order since they're independent of each other.
specify init, then /speckit.constitution, /speckit.specify, /speckit.plan, /speckit.tasks, and finally /speckit.implement.
Start with /speckit.implement and work backward to /speckit.specify.
You must answer all questions before checking your work.
War dës Säit hëllefräich?
Braucht Dir Hëllef mat dësem Theema?
Wëllt Dir probéieren, Ask Learn ze benotzen, fir Iech duerch dëst Theema ze leeden oder et méi kloer ze maachen?