Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

`/prompts:speckit.clarify` with codex CLI offers recommended actions with no clarifying question

オープン 初心者向け
#1,147 コメント 7 件 リアクション 5 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
76/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
markdown
領域
ai, tooling

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

stale

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.md to 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

主要言語
Python
スター
138k
フォーク
12.4k
平均マージ
3日 4時間
マージ済み PR(30日)
154

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/spec-kit のほかの issue

github/spec-kit の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。