From 12035f42ab9b623403995e9a2ac465f867263f1b Mon Sep 17 00:00:00 2001 From: Emi Date: Tue, 20 Jan 2026 11:58:47 +0100 Subject: [PATCH 1/2] docs: Fix doc missing step --- docs/quickstart.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/docs/quickstart.md b/docs/quickstart.md index 4d3b863b35..c53b34b2aa 100644 --- a/docs/quickstart.md +++ b/docs/quickstart.md @@ -81,6 +81,9 @@ Then, use the `/speckit.implement` slash command to execute the plan. /speckit.implement ``` +> [!TIP] +> **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. + ## Detailed Example: Building Taskify Here's a complete example of building a team productivity platform: @@ -127,7 +130,15 @@ Validate the specification checklist using the `/speckit.checklist` command: /speckit.checklist ``` -### Step 5: Generate Technical Plan with `/speckit.plan` +### Step 5: Define Tasks + +Generate an actionable task list using the `/speckit.tasks` command: + +```bash +/speckit.tasks +``` + +### Step 6: Generate Technical Plan with `/speckit.plan` Be specific about your tech stack and technical requirements: @@ -135,7 +146,7 @@ Be specific about your tech stack and technical requirements: /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. ``` -### Step 6: Validate and Implement +### Step 7: Validate and Implement Have your AI agent audit the implementation plan using `/speckit.analyze`: @@ -149,6 +160,9 @@ Finally, implement the solution: /speckit.implement ``` +> [!TIP] +> **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. + ## Key Principles - **Be explicit** about what you're building and why From 0f5766aba8497d67a085f80e23df9cb722ea1adf Mon Sep 17 00:00:00 2001 From: Emi Date: Tue, 20 Jan 2026 12:04:26 +0100 Subject: [PATCH 2/2] docs: Update steps for generating technical plan and defining tasks --- docs/quickstart.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/quickstart.md b/docs/quickstart.md index c53b34b2aa..37d431dbad 100644 --- a/docs/quickstart.md +++ b/docs/quickstart.md @@ -130,20 +130,20 @@ Validate the specification checklist using the `/speckit.checklist` command: /speckit.checklist ``` -### Step 5: Define Tasks +### Step 5: Generate Technical Plan with `/speckit.plan` -Generate an actionable task list using the `/speckit.tasks` command: +Be specific about your tech stack and technical requirements: ```bash -/speckit.tasks +/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. ``` -### Step 6: Generate Technical Plan with `/speckit.plan` +### Step 6: Define Tasks -Be specific about your tech stack and technical requirements: +Generate an actionable task list using the `/speckit.tasks` command: ```bash -/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. +/speckit.tasks ``` ### Step 7: Validate and Implement