💫 Toolkit to help you get started with SDD or any other process!
Update templates/commands/plan.md
Den Delimarskya0faa222c8ee
diff --git a/templates/commands/plan.md b/templates/commands/plan.mdindex c029c5b8b..32522c232 100644--- a/templates/commands/plan.md+++ b/templates/commands/plan.md@@ -14,7 +14,7 @@ $ARGUMENTSGiven 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