From 5b2cd0d3e483474131147de1b92cb14be35b9f3c Mon Sep 17 00:00:00 2001
From: marcelsafin <179933638+marcelsafin@users.noreply.github.com>
Date: Thu, 9 Jul 2026 00:59:49 +0200
Subject: [PATCH] fix(templates): correct phase numbering in plan.md

The plan command's outline listed two bullets labeled Phase 1 and the
completion report said the command ends after "Phase 2 planning",
but the Phases section only defines Phase 0 and Phase 1. Phase 2
(tasks.md) belongs to the tasks command, as plan-template.md states.

The duplicated "Phase 1: Update agent context" bullet is a leftover
from before the agent-context extension: core no longer ships an agent
script, and the update runs via the extension's after_plan hook.

Fixes #1036

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---
 templates/commands/plan.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/templates/commands/plan.md b/templates/commands/plan.md
index e82bd4b303..063fc911b3 100644
--- a/templates/commands/plan.md
+++ b/templates/commands/plan.md
@@ -68,7 +68,6 @@ You **MUST** consider the user input before proceeding (if not empty).
    - Evaluate gates (ERROR if violations unjustified)
    - Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
    - Phase 1: Generate data-model.md, contracts/, quickstart.md
-   - Phase 1: Update agent context by running the agent script
    - Re-evaluate Constitution Check post-design
 
 ## Mandatory Post-Execution Hooks
@@ -107,7 +106,7 @@ Check if `.specify/extensions.yml` exists in the project root.
 
 ## Completion Report
 
-Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
+Command ends after Phase 1 design. Report branch, IMPL_PLAN path, and generated artifacts.
 
 ## Phases