`/prompts:speckit.clarify` with codex CLI offers recommended actions with no clarifying question
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 76/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- Python
- Stelle
- 138k
- Fork
- 12.4k
- Merge medio
- 3g 4h
- PR unite (30g)
- 154
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/spec-kit
-
enhancement needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
enhancement needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
-
enhancement needs-triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
-
enhancement needs-triage triage-can-wait
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
Tutte le issue di github/spec-kit
Issue simili
-
essnmx good first issue
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 95/100
-
[Feature] 奇物选择添加优先级 Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Giskard-AI/giskard-oss#2840 · 1 commento ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Apertaarea: repo bug perceived difficulty: 2
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
yeti-platform/yeti#1380 ·