Skip to content

Commit 12035f4

Browse files
committed
docs: Fix doc missing step
1 parent 9111699 commit 12035f4

File tree

1 file changed

+16
-2
lines changed

1 file changed

+16
-2
lines changed

docs/quickstart.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,9 @@ Then, use the `/speckit.implement` slash command to execute the plan.
8181
/speckit.implement
8282
```
8383

84+
> [!TIP]
85+
> **Phased Implementation**: For complex projects, implement in phases to avoid overwhelming the agent's context. Start with core functionality, validate it works, then add features incrementally.
86+
8487
## Detailed Example: Building Taskify
8588

8689
Here's a complete example of building a team productivity platform:
@@ -127,15 +130,23 @@ Validate the specification checklist using the `/speckit.checklist` command:
127130
/speckit.checklist
128131
```
129132
130-
### Step 5: Generate Technical Plan with `/speckit.plan`
133+
### Step 5: Define Tasks
134+
135+
Generate an actionable task list using the `/speckit.tasks` command:
136+
137+
```bash
138+
/speckit.tasks
139+
```
140+
141+
### Step 6: Generate Technical Plan with `/speckit.plan`
131142
132143
Be specific about your tech stack and technical requirements:
133144
134145
```bash
135146
/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.
136147
```
137148
138-
### Step 6: Validate and Implement
149+
### Step 7: Validate and Implement
139150
140151
Have your AI agent audit the implementation plan using `/speckit.analyze`:
141152
@@ -149,6 +160,9 @@ Finally, implement the solution:
149160
/speckit.implement
150161
```
151162
163+
> [!TIP]
164+
> **Phased Implementation**: For large projects like Taskify, consider implementing in phases (e.g., Phase 1: Basic project/task structure, Phase 2: Kanban functionality, Phase 3: Comments and assignments). This prevents context saturation and allows for validation at each stage.
165+
152166
## Key Principles
153167
154168
- **Be explicit** about what you're building and why

0 commit comments

Comments
 (0)