fix(ce-compound): require question tool for "What's next?" prompt#460
Merged
Conversation
The success output's "What's next?" options were presented as plain text, not using the platform's blocking question tool. This meant the workflow could end without the user's selection being captured. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
…ge stores Captures the design rationale behind the discoverability check added in feat/compound-discoverability-check — ensuring project instruction files surface docs/solutions/ so agents in fresh sessions can find it. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
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
1 participant
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.
The success output's "What's next?" options were presented as plain text rather than using the platform's blocking question tool. This meant the workflow could end its turn without the user's selection being captured — the options were decorative, not interactive.
Adds an explicit instruction after the success output block to use
AskUserQuestion(Claude Code) /request_user_input(Codex) /ask_user(Gemini), with a fallback for environments without a question tool.Also includes a learning document capturing the discoverability check pattern from
feat/compound-discoverability-check.🤖 Generated with Claude Opus 4.6 (1M context, extended thinking) via Claude Code