clarify: require real interrogatives, ban topic-label questions - #3745
Merged
Conversation
Agents often present topic labels or bare requirement ids as "questions", which are not answerable on their own. Require a full interrogative under **Question:**, a plain-language stake sentence, then Recommended/options. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies the /speckit.clarify question format to require standalone interrogatives and plain-language context.
Changes:
- Requires
**Question:**prompts ending in a question mark. - Prohibits topic labels and IDs as questions.
- Adds a “Why it matters” sentence before options.
Show a summary per file
| File | Description |
|---|---|
templates/commands/clarify.md |
Strengthens clarification-question formatting guidance. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Medium
mnriem
requested changes
Jul 27, 2026
mnriem
left a comment
mnriem
left a comment
Collaborator
There was a problem hiding this comment.
Please address Copilot feedback
Contributor
Author
"must stand on its own" can refer to meaning or position. I have removed the ambiguity: "must make sense on its own" |
Resolves Copilot feedback: an interrogative ending in ? cannot also have a parenthesized id "at the end of the question." Exact format is now `**Question:** <interrogative>?` or `**Question:** <interrogative>? (FR-023)`. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Author
|
Addressed Copilot’s ID/
Ready for re-review. |
mnriem
self-requested a review
July 28, 2026 12:57
mnriem
approved these changes
Jul 28, 2026
Collaborator
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarify agents often present topic labels or bare requirement ids as "questions" (e.g.
Acceptance device/runtime matrix (FR-023)), which are not answerable on their own. This extends the question-first UX direction from #1777: every turn must lead with a full interrogative under**Question:**, add one plain-language stake sentence, then Recommended/options. Requirement ids belong only in trailing parentheses.Test plan
/speckit.clarifyon a spec with open NEEDS CLARIFICATION items**Question:** …?(not a topic heading)Made with Cursor