Add escaping guidelines to command templates

This commit is contained in:
Daniil Sobolev
2025-10-08 18:00:14 +03:00
parent 719ba762bc
commit af2b14e9be
7 changed files with 8 additions and 5 deletions

View File

@@ -26,6 +26,7 @@ Execution steps:
- `FEATURE_SPEC`
- (Optionally capture `IMPL_PLAN`, `TASKS` for future chained flows.)
- If JSON parsing fails, abort and instruct user to re-run `/speckit.specify` or verify feature branch environment.
- 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").
2. Load the current spec file. Perform a structured ambiguity & coverage scan using this taxonomy. For each category, mark status: Clear / Partial / Missing. Produce an internal coverage map used for prioritization (do not output raw map unless no questions will be asked).