`/prompts:speckit.clarify` with codex CLI offers recommended actions with no clarifying question
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 76/100
Línea de trabajo
Comienza con .codex/prompts/speckit.clarify.md e inspecciona cómo se obtiene o regenera este prompt generado. Verifica que las instrucciones de selección múltiple repitan la pregunta antes de las recomendaciones y, a continuación, usa el paso de generación o validación documentado del repositorio; estará terminado cuando la salida generada incluya la pregunta de aclaración antes de sus opciones.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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
- Lenguaje dominante
- Python
- Estrellas
- 138k
- Forks
- 12.4k
- Merge medio
- 3 d 4 h
- PR fusionados (30 d)
- 154
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/spec-kit
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
enhancement needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
enhancement needs-triage triage-can-wait
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Todos los issues de github/spec-kit
Issues similares
-
bug confirmed issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
open-webui/open-webui#30750 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100