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
Use the **`/constitution`** command to create your project's governing principles and development guidelines that will guide all subsequent development.
76
+
Use the **`/speckit.constitution`** command to create your project's governing principles and development guidelines that will guide all subsequent development.
77
77
78
78
```bash
79
-
/constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements
79
+
/speckit.constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements
80
80
```
81
81
82
82
### 3. Create the spec
83
83
84
-
Use the **`/specify`** command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
84
+
Use the **`/speckit.specify`** command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
85
85
86
86
```bash
87
-
/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.
87
+
/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.
88
88
```
89
89
90
90
### 4. Create a technical implementation plan
91
91
92
-
Use the **`/plan`** command to provide your tech stack and architecture choices.
92
+
Use the **`/speckit.plan`** command to provide your tech stack and architecture choices.
93
93
94
94
```bash
95
-
/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.
95
+
/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.
96
96
```
97
97
98
98
### 5. Break down into tasks
99
99
100
-
Use **`/tasks`** to create an actionable task list from your implementation plan.
100
+
Use **`/speckit.tasks`** to create an actionable task list from your implementation plan.
101
101
102
102
```bash
103
-
/tasks
103
+
/speckit.tasks
104
104
```
105
105
106
106
### 6. Execute implementation
107
107
108
-
Use **`/implement`** to execute all tasks and build your feature according to the plan.
108
+
Use **`/speckit.implement`** to execute all tasks and build your feature according to the plan.
109
109
110
110
```bash
111
-
/implement
111
+
/speckit.implement
112
112
```
113
113
114
114
For detailed step-by-step instructions, see our [comprehensive guide](./spec-driven.md).
@@ -211,29 +211,29 @@ After running `specify init`, your AI coding agent will have access to these sla
211
211
212
212
Essential commands for the Spec-Driven Development workflow:
|`SPECIFY_FEATURE`| Override feature detection for non-Git repositories. Set to the feature directory name (e.g., `001-photo-albums`) to work on a specific feature when not using Git branches.<br/>**Must be set in the context of the agent you're working with prior to using `/plan` or follow-up commands. |
236
+
|`SPECIFY_FEATURE`| Override feature detection for non-Git repositories. Set to the feature directory name (e.g., `001-photo-albums`) to work on a specific feature when not using Git branches.<br/>**Must be set in the context of the agent you're working with prior to using `/speckit.plan` or follow-up commands. |
237
237
238
238
## 📚 Core philosophy
239
239
@@ -354,19 +354,19 @@ Go to the project folder and run your AI agent. In our example, we're using `cla
354
354
355
355
356
356
357
-
You will know that things are configured correctly if you see the `/constitution`, `/specify`, `/plan`, `/tasks`, and `/implement` commands available.
357
+
You will know that things are configured correctly if you see the `/speckit.constitution`, `/speckit.specify`, `/speckit.plan`, `/speckit.tasks`, and `/speckit.implement` commands available.
358
358
359
-
The first step should be establishing your project's governing principles using the `/constitution` command. This helps ensure consistent decision-making throughout all subsequent development phases:
359
+
The first step should be establishing your project's governing principles using the `/speckit.constitution` command. This helps ensure consistent decision-making throughout all subsequent development phases:
360
360
361
361
```text
362
-
/constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements. Include governance for how these principles should guide technical decisions and implementation choices.
362
+
/speckit.constitution Create principles focused on code quality, testing standards, user experience consistency, and performance requirements. Include governance for how these principles should guide technical decisions and implementation choices.
363
363
```
364
364
365
365
This step creates or updates the `.specify/memory/constitution.md` file with your project's foundational guidelines that the AI agent will reference during specification, planning, and implementation phases.
366
366
367
367
### **STEP 2:** Create project specifications
368
368
369
-
With your project principles established, you can now create the functional specifications. Use the `/specify` command and then provide the concrete requirements for the project you want to develop.
369
+
With your project principles established, you can now create the functional specifications. Use the `/speckit.specify` command and then provide the concrete requirements for the project you want to develop.
370
370
371
371
>[!IMPORTANT]
372
372
>Be as explicit as possible about _what_ you are trying to build and _why_. **Do not focus on the tech stack at this point**.
@@ -426,12 +426,12 @@ With the baseline specification created, you can go ahead and clarify any of the
426
426
You should run the structured clarification workflow **before** creating a technical plan to reduce rework downstream.
427
427
428
428
Preferred order:
429
-
1. Use `/clarify` (structured) – sequential, coverage-based questioning that records answers in a Clarifications section.
429
+
1. Use `/speckit.clarify` (structured) – sequential, coverage-based questioning that records answers in a Clarifications section.
430
430
2. Optionally follow up with ad-hoc free-form refinement if something still feels vague.
431
431
432
432
If you intentionally want to skip clarification (e.g., spike or exploratory prototype), explicitly state that so the agent doesn't block on missing clarifications.
433
433
434
-
Example free-form refinement prompt (after `/clarify` if still needed):
434
+
Example free-form refinement prompt (after `/speckit.clarify` if still needed):
435
435
436
436
```text
437
437
For each sample project or project that you create there should be a variable number of tasks between 5 and 15
@@ -449,7 +449,7 @@ It's important to use the interaction with Claude Code as an opportunity to clar
449
449
450
450
### **STEP 4:** Generate a plan
451
451
452
-
You can now be specific about the tech stack and other technical requirements. You can use the `/plan` command that is built into the project template with a prompt like this:
452
+
You can now be specific about the tech stack and other technical requirements. You can use the `/speckit.plan` command that is built into the project template with a prompt like this:
453
453
454
454
```text
455
455
We are going to generate this using .NET Aspire, using Postgres as the database. The frontend should use
@@ -535,13 +535,13 @@ You can also ask Claude Code (if you have the [GitHub CLI](https://docs.github.c
535
535
536
536
### STEP 6: Implementation
537
537
538
-
Once ready, use the `/implement` command to execute your implementation plan:
538
+
Once ready, use the `/speckit.implement` command to execute your implementation plan:
539
539
540
540
```text
541
-
/implement
541
+
/speckit.implement
542
542
```
543
543
544
-
The `/implement` command will:
544
+
The `/speckit.implement` command will:
545
545
- Validate that all prerequisites are in place (constitution, spec, plan, and tasks)
546
546
- Parse the task breakdown from `tasks.md`
547
547
- Execute tasks in the correct order, respecting dependencies and parallel execution markers
Use the `/specify` command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
25
+
Use the `/speckit.specify` command to describe what you want to build. Focus on the **what** and **why**, not the tech stack.
26
26
27
27
```bash
28
-
/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.
28
+
/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.
29
29
```
30
30
31
31
### 3. Create a Technical Implementation Plan
32
32
33
-
Use the `/plan` command to provide your tech stack and architecture choices.
33
+
Use the `/speckit.plan` command to provide your tech stack and architecture choices.
34
34
35
35
```bash
36
-
/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.
36
+
/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.
37
37
```
38
38
39
39
### 4. Break Down and Implement
40
40
41
-
Use `/tasks` to create an actionable task list, then ask your agent to implement the feature.
41
+
Use `/speckit.tasks` to create an actionable task list, then ask your agent to implement the feature.
42
42
43
43
## Detailed Example: Building Taskify
44
44
45
45
Here's a complete example of building a team productivity platform:
46
46
47
-
### Step 1: Define Requirements with `/specify`
47
+
### Step 1: Define Requirements with `/speckit.specify`
48
48
49
49
```text
50
50
Develop Taskify, a team productivity platform. It should allow users to create projects, add team members,
@@ -81,7 +81,7 @@ Also validate the specification checklist:
81
81
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.
82
82
```
83
83
84
-
### Step 3: Generate Technical Plan with `/plan`
84
+
### Step 3: Generate Technical Plan with `/speckit.plan`
85
85
86
86
Be specific about your tech stack and technical requirements:
0 commit comments