docs(commands): fix stale path refs, phantom phase, duplicate numbering

Four small doc corrections in templates/commands/*.md, surfaced while
integrating Spec Kit into a Claude Code project:

- plan.md: "Command ends after Phase 2 planning" referenced a phase
  that doesn't exist in this file. Only Phase 0 (research) and Phase 1
  (data-model, contracts, quickstart) are defined; the command actually
  ends after Phase 1. Updated the terminal step to match.

- implement.md: step 5 "Task phases" parse-list was "Setup, Tests, Core,
  Integration, Polish" — an older layered taxonomy that doesn't match
  what tasks.md currently emits ("Setup, Foundational, User Stories in
  priority order, Polish"). The mismatch meant /speckit.implement
  wouldn't find any of the phase headers it was looking for. Aligned
  the parse list with tasks.md's actual output.

- constitution.md: step 4 instructed the user to "Read each command
  file in .specify/templates/commands/*.md" — that path isn't
  materialized on every integration install (e.g., Claude Code puts
  command files under .claude/skills/speckit-*/SKILL.md; Copilot uses
  .github/prompts/). Softened the reference to name the likely
  integration-specific locations and note the path varies.

- taskstoissues.md: four consecutive `1.` source-level numbered items
  in the Outline block. Markdown auto-renumbers on render, but the
  source reads oddly and encourages the same pattern in new specs.
  Renumbered to 1/2/3/4.

All four reproduce on main as of this branch-off; none touch behavior
beyond what each docstring already describes.

## AI disclosure

This PR was drafted with assistance from Claude (Opus 4.7) while
integrating Spec Kit into a live project. The rationale for each fix
came from actually running the affected commands end-to-end through
an agent; the one-line edits are mechanical corrections to existing
text, not new guidance.

Author: vsima

templates/commands/constitution.md

@@ -80,7 +80,7 @@ Follow this execution flow:
    - Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
    - Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
    - Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
-   - Read each command file in `.specify/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
+   - Review each installed command file to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required. Paths vary by integration — e.g. `.claude/skills/speckit-*/SKILL.md` (Claude Code), `.github/prompts/speckit.*.prompt.md` (Copilot), or `.specify/templates/commands/*.md` when a preset ships them. Consult the active integration's skills/commands directory rather than assuming a single location.
    - Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
 
 5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):

templates/commands/implement.md

@@ -135,7 +135,7 @@ You **MUST** consider the user input before proceeding (if not empty).
    - **Kubernetes/k8s**: `*.secret.yaml`, `secrets/`, `.kube/`, `kubeconfig*`, `*.key`, `*.crt`
 
 5. Parse tasks.md structure and extract:
-   - **Task phases**: Setup, Tests, Core, Integration, Polish
+   - **Task phases**: Setup, Foundational, User Stories (one phase per story, in priority order), Polish (matches the phase structure emitted by `/speckit.tasks`; see `templates/commands/tasks.md`)
    - **Task dependencies**: Sequential vs parallel execution rules
    - **Task details**: ID, description, file paths, parallel markers [P]
    - **Execution flow**: Order and dependency requirements

templates/commands/plan.md

@@ -70,7 +70,7 @@ You **MUST** consider the user input before proceeding (if not empty).
    - Phase 1: Update agent context by running the agent script
    - Re-evaluate Constitution Check post-design
 
-4. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
+4. **Stop and report**: Command ends after Phase 1 (data-model & contracts). Report branch, IMPL_PLAN path, and generated artifacts.
 
 5. **Check for extension hooks**: After reporting, check if `.specify/extensions.yml` exists in the project root.
    - If it exists, read it and look for entries under the `hooks.after_plan` key

templates/commands/taskstoissues.md

@@ -51,8 +51,8 @@ You **MUST** consider the user input before proceeding (if not empty).
 ## Outline
 
 1. Run `{SCRIPT}` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-1. From the executed script, extract the path to **tasks**.
-1. Get the Git remote by running:
+2. From the executed script, extract the path to **tasks**.
+3. Get the Git remote by running:
 
 ```bash
 git config --get remote.origin.url
@@ -61,7 +61,7 @@ git config --get remote.origin.url
 > [!CAUTION]
 > ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL
 
-1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
+4. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
 
 > [!CAUTION]
 > UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL