`/prompts:speckit.clarify` with codex CLI offers recommended actions with no clarifying question
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
Research direction
Start with .codex/prompts/speckit.clarify.md and inspect how this generated prompt is sourced or regenerated. Verify that multiple-choice instructions restate the question before recommendations, then use the repository's documented generation or validation step; done when the generated output includes the clarifying question before its options.
Written by the indexing model from the issue text.
Description
Context:
I have established the project principles with /prompt:/speckit.constitution.
No edit's or changes have been requested of the originally generated markdown files.
I have then generated a baseline specification for example: /prompts:speckit.specify Define a delivery strategy for the project that slices features vertically
I have then used a prompt as an example below to ensure a minimum required clarifying questions are being asked:
/prompts:speckit.clarify DOMAIN & DATA MODEL — Generate the smallest set of questions to lock the core data contracts for the program (client-first). Ask for: (1) canonical field lists, types, and units for Contacts; (2) identifiers & keys and allowed character sets
...etc
I will then receive an output similar to below:
• Recommended: Option A – Explanation of the option
Option Description A Do Step A. B Do Step B. C Do Step C. Short Provide a different short answer (<=5 words). You can reply with the option letter (e.g., "A"), accept the recommendation by saying "yes" or "recommended", or provide your own short answer.
Issue
The output will only show the recommended steps, but does not give any context to what question is being asked
Expected Result
• DOMAIN & DATA MODEL - How will the canonical field lists, types, and units for Contacts be displayed?
• Recommended: Option A – Explanation of the option
Option Description A Do Step A. B Do Step B. C Do Step C. Short Provide a different short answer (<=5 words). You can reply with the option letter (e.g., "A"), accept the recommendation by saying "yes" or "recommended", or provide your own short answer.
Recommended Fix
- Update the generated
.codex\prompts\speckit.clarify.mdto include an additional line similar to below:
diff --git a\.codex\prompts\speckit.clarify.md b\.codex\prompts\speckit.clarify.md
--- a\.codex\prompts\speckit.clarify.md
+++ b\.codex\prompts\speckit.clarify.md
@@ -1,15 +1,16 @@
4. Sequential questioning loop (interactive):
- Present EXACTLY ONE question at a time.
- For multiple-choice questions:
+ - Before any recommendation, restate the question verbatim on its own line as `**Question:** <original question>`.
- **Analyze all options** and determine the **most suitable option** based on:
- Best practices for the project type
- Common patterns in similar implementations
- Risk reduction (security, performance, maintainability)
- Alignment with any explicit project goals or constraints visible in the spec
- Present your **recommended option prominently** at the top with clear reasoning (1-2 sentences explaining why this is the best choice).
- Format as: `**Recommended:** Option [X] - <reasoning>`
- Then render all options as a Markdown table:
| Option | Description |
|--------|-------------|
| A | <Option A description> |
| B | <Option B description> |
| C | <Option C description> (add D/E as needed up to 5) |
| Short | Provide a different short answer (<=5 words) (Include only if free-form alternative is appropriate) |
Environment
Windows 11
Codex CLI - Run in WSL2 project virtual environment
- Dominant language
- Python
- Stars
- 138k
- Forks
- 12.4k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 136
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/spec-kit
-
triage-can-wait
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement needs-triage triage-can-wait
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bundle-submission needs-info triage-can-wait validation-failed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
author-awaiting enhancement needs-triage preset-submission triage-can-wait validation-failed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
author-awaiting enhancement extension-submission needs-triage triage-can-wait validation-failed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Similar issues
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/agentscope#2775 ·
-
comp/desktop P3 type/bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
NousResearch/hermes-agent#118866 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
apache/cloudstack#14222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100