Spec Kit aims to transform the traditional model of "writing code first, then writing specifications" or "treating specs merely as documentation" by elevating specifications into executable, continuously evolving core assets. In other words, "you first define what you want to achieve (what/why)" before discussing "how to do it (how)".
The project provides a CLI tool specify, which can be used to initialize project scaffolding, generate specification templates, create task lists, and more.
The supported workflow can be broken down into several stages (typically four steps):
Specify: Define the project's goals, user scenarios, and success criteria.
Plan: After clarifying "what to do," define the technical approach, architecture, technology stack selection, and constraints for "how to do it."
Tasks: Break down the plan into executable, fine-grained tasks to facilitate implementation, review, and iteration.
Implement: Execute coding, testing, and integration based on the tasks, and make corrections based on specification feedback.
The project structure also includes a "constitution.md" file—used to define non-negotiable principles or engineering constraints for the project (such as test coverage requirements, technology stack standards, coding style guidelines, etc.).
Although it claims compatibility with various technology stacks (language-agnostic), the CLI tool is written in Python and requires Python 3.11+.
Comments
No comments yet
Be the first to comment