You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/quickstart.md
+88-47Lines changed: 88 additions & 47 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,16 +2,24 @@
2
2
3
3
This guide will help you get started with Spec-Driven Development using Spec Kit.
4
4
5
-
> NEW: All automation scripts now provide both Bash (`.sh`) and PowerShell (`.ps1`) variants. The `specify` CLI auto-selects based on OS unless you pass `--script sh|ps`.
5
+
> [!NOTE]
6
+
> All automation scripts now provide both Bash (`.sh`) and PowerShell (`.ps1`) variants. The `specify` CLI auto-selects based on OS unless you pass `--script sh|ps`.
6
7
7
-
## The 4-Step Process
8
+
## The 6-Step Process
8
9
9
-
### 1. Install Specify
10
+
> [!TIP]
11
+
> **Context Awareness**: Spec Kit commands automatically detect the active feature based on your current Git branch (e.g., `001-feature-name`). To switch between different specifications, simply switch Git branches.
10
12
11
-
Initialize your project depending on the coding agent you're using:
13
+
### Step 1: Install Specify
14
+
15
+
**In your terminal**, run the `specify` CLI command to initialize your project:
uvx --from git+https://github.com/github/spec-kit.git specify init <PROJECT_NAME> --script sh # Force POSIX shell
22
30
```
23
31
24
-
### 2. Create the Spec
32
+
### Step 2: Define Your Constitution
25
33
26
-
Use the `/speckit.specify`command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
34
+
**In your AI Agent's chat interface**, use the `/speckit.constitution` slash command to establish the core rules and principles for your project. You should provide your project's specific principles as arguments.
27
35
28
-
```bash
36
+
```markdown
37
+
/speckit.constitution This project follows a "Library-First" approach. All features must be implemented as standalone libraries first. We use TDD strictly. We prefer functional programming patterns.
38
+
```
39
+
40
+
### Step 3: Create the Spec
41
+
42
+
**In the chat**, use the `/speckit.specify` slash command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
43
+
44
+
```markdown
29
45
/speckit.specify Build an application that can help me organize my photos in separate photo albums. Albums are grouped by date and can be re-organized by dragging and dropping on the main page. Albums are never in other nested albums. Within each album, photos are previewed in a tile-like interface.
30
46
```
31
47
32
-
### 3. Create a Technical Implementation Plan
48
+
### Step 4: Refine the Spec
33
49
34
-
Use the `/speckit.plan`command to provide your tech stack and architecture choices.
50
+
**In the chat**, use the `/speckit.clarify` slash command to identify and resolve ambiguities in your specification. You can provide specific focus areas as arguments.
35
51
36
52
```bash
53
+
/speckit.clarify Focus on security and performance requirements.
54
+
```
55
+
56
+
### Step 5: Create a Technical Implementation Plan
57
+
58
+
**In the chat**, use the `/speckit.plan` slash command to provide your tech stack and architecture choices.
59
+
60
+
```markdown
37
61
/speckit.plan The application uses Vite with minimal number of libraries. Use vanilla HTML, CSS, and JavaScript as much as possible. Images are not uploaded anywhere and metadata is stored in a local SQLite database.
38
62
```
39
63
40
-
### 4. Break Down and Implement
64
+
### Step 6: Break Down and Implement
65
+
66
+
**In the chat**, use the `/speckit.tasks` slash command to create an actionable task list.
67
+
68
+
```markdown
69
+
/speckit.tasks
70
+
```
71
+
72
+
Optionally, validate the plan with `/speckit.analyze`:
41
73
42
-
Use `/speckit.tasks` to create an actionable task list, then ask your agent to implement the feature.
74
+
```markdown
75
+
/speckit.analyze
76
+
```
77
+
78
+
Then, use the `/speckit.implement` slash command to execute the plan.
79
+
80
+
```markdown
81
+
/speckit.implement
82
+
```
43
83
44
84
## Detailed Example: Building Taskify
45
85
46
86
Here's a complete example of building a team productivity platform:
47
87
48
-
### Step 1: Define Requirements with `/speckit.specify`
88
+
### Step 1: Define Constitution
89
+
90
+
Initialize the project's constitution to set ground rules:
91
+
92
+
```markdown
93
+
/speckit.constitution Taskify is a "Security-First" application. All user inputs must be validated. We use a microservices architecture. Code must be fully documented.
94
+
```
95
+
96
+
### Step 2: Define Requirements with `/speckit.specify`
49
97
50
98
```text
51
99
Develop Taskify, a team productivity platform. It should allow users to create projects, add team members,
@@ -54,58 +102,51 @@ let's call it "Create Taskify," let's have multiple users but the users will be
54
102
I want five users in two different categories, one product manager and four engineers. Let's create three
55
103
different sample projects. Let's have the standard Kanban columns for the status of each task, such as "To Do,"
56
104
"In Progress," "In Review," and "Done." There will be no login for this application as this is just the very
57
-
first testing thing to ensure that our basic features are set up. For each task in the UI for a task card,
58
-
you should be able to change the current status of the task between the different columns in the Kanban work board.
59
-
You should be able to leave an unlimited number of comments for a particular card. You should be able to, from that task
60
-
card, assign one of the valid users. When you first launch Taskify, it's going to give you a list of the five users to pick
61
-
from. There will be no password required. When you click on a user, you go into the main view, which displays the list of
62
-
projects. When you click on a project, you open the Kanban board for that project. You're going to see the columns.
63
-
You'll be able to drag and drop cards back and forth between different columns. You will see any cards that are
64
-
assigned to you, the currently logged in user, in a different color from all the other ones, so you can quickly
65
-
see yours. You can edit any comments that you make, but you can't edit comments that other people made. You can
66
-
delete any comments that you made, but you can't delete comments anybody else made.
105
+
first testing thing to ensure that our basic features are set up.
67
106
```
68
107
69
-
### Step 2: Refine the Specification
108
+
### Step 3: Refine the Specification
70
109
71
-
After the initial specification is created, clarify any missing requirements:
110
+
Use the `/speckit.clarify` command to interactively resolve any ambiguities in your specification. You can also provide specific details you want to ensure are included.
72
111
73
-
```text
74
-
For each sample project or project that you create there should be a variable number of tasks between 5 and 15
75
-
tasks for each one randomly distributed into different states of completion. Make sure that there's at least
76
-
one task in each stage of completion.
112
+
```bash
113
+
/speckit.clarify I want to clarify the task card details. For each task in the UI fora task card, you should be able to change the current status of the task between the different columnsin the Kanban work board. You should be able to leave an unlimited number of comments for a particular card. You should be able to, from that task card, assign one of the valid users.
77
114
```
78
115
79
-
Also validate the specification checklist:
116
+
You can continue to refine the spec with more details using `/speckit.clarify`:
80
117
81
-
```text
82
-
Read the review and acceptance checklist, and check off each item in the checklist if the feature spec meets the criteria. Leave it empty if it does not.
118
+
```bash
119
+
/speckit.clarify When you first launch Taskify, it's going to give you a list of the five users to pick from. There will be no password required. When you click on a user, you go into the main view, which displays the list of projects. When you click on a project, you open the Kanban board for that project. You're going to see the columns. You'll be able to drag and drop cards back and forth between different columns. You will see any cards that are assigned to you, the currently logged in user, in a different color from all the other ones, so you can quickly see yours. You can edit any comments that you make, but you can't edit comments that other people made. You can delete any comments that you made, but you can't delete comments anybody else made.
83
120
```
84
121
85
-
### Step 3: Generate Technical Plan with `/speckit.plan`
122
+
### Step 4: Validate the Spec
123
+
124
+
Validate the specification checklist using the `/speckit.checklist` command:
125
+
126
+
```bash
127
+
/speckit.checklist
128
+
```
129
+
130
+
### Step 5: Generate Technical Plan with `/speckit.plan`
86
131
87
132
Be specific about your tech stack and technical requirements:
88
133
89
-
```text
90
-
We are going to generate this using .NET Aspire, using Postgres as the database. The frontend should use
91
-
Blazor server with drag-and-drop task boards, real-time updates. There should be a REST API created with a projects API,
92
-
tasks API, and a notifications API.
134
+
```bash
135
+
/speckit.plan We are going to generate this using .NET Aspire, using Postgres as the database. The frontend should use Blazor server with drag-and-drop task boards, real-time updates. There should be a REST API created with a projects API, tasks API, and a notifications API.
93
136
```
94
137
95
-
### Step 4: Validate and Implement
138
+
### Step 6: Validate and Implement
96
139
97
-
Have your AI agent audit the implementation plan:
140
+
Have your AI agent audit the implementation plan using `/speckit.analyze`:
98
141
99
-
```text
100
-
Now I want you to go and audit the implementation plan and the implementation detail files.
101
-
Read through it with an eye on determining whether or not there is a sequence of tasks that you need
102
-
to be doing that are obvious from reading this. Because I don't know if there's enough here.
0 commit comments