From a0faa222c8ee685c1139009f6235a716bfb62b49 Mon Sep 17 00:00:00 2001
From: Den Delimarsky <53200638+localden@users.noreply.github.com>
Date: Mon, 22 Sep 2025 21:12:27 -0700
Subject: [PATCH] Update templates/commands/plan.md

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

diff --git a/templates/commands/plan.md b/templates/commands/plan.md
index c029c5b..32522c2 100644
--- a/templates/commands/plan.md
+++ b/templates/commands/plan.md
@@ -14,7 +14,7 @@ $ARGUMENTS
 Given the implementation details provided as an argument, do this:
 
 1. Run `{SCRIPT}` from the repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. All future file paths must be absolute.
-   - BEFORE proceeding, inspect FEATURE_SPEC for a `## Clarifications` section with at least one `Session` subheading. If missing or clearly ambiguous areas remain (vague adjectives, unresolved critical choices), PAUSE and instruct the user to run `/clarify` first to reduce rework. Only continue if: (a) Clarifications exist OR (b) an explicit user override is provided (e.g., "proceed without clarify"). Do not attempt to fabricate clarifications yourself.
+   - BEFORE proceeding, inspect FEATURE_SPEC for a `## Clarifications` section with at least one `Session` subheading. If missing or clearly ambiguous areas remain (vague adjectives, unresolved critical choices), PAUSE and instruct the user to run `/clarify` first to reduce rework. Only continue if: (a) Clarifications exist OR (b) an explicit user override is provided (e.g., "proceed without clarification"). Do not attempt to fabricate clarifications yourself.
 2. Read and analyze the feature specification to understand:
    - The feature requirements and user stories
    - Functional and non-functional requirements