-
Notifications
You must be signed in to change notification settings - Fork 9.1k
office-hours: design doc not visible to user when AskUserQuestion requests approval #879
Description
Problem
When the /office-hours skill completes a design document and asks the user for approval via AskUserQuestion, the user cannot see the document content. The document is written to ~/.gstack/projects/ but the approval prompt only shows a summary — the user has to repeatedly ask "show me the full doc" before they can make a decision.
Tool outputs (e.g., cat via Bash tool) are often collapsed/hidden in the Claude Code UI, so even when the assistant tries to output the file, users may not see it.
Current behavior
- Design doc is written to
~/.gstack/projects/{slug}/ - AskUserQuestion asks "Approve / Revise / Start over"
- User cannot see the document — they have to ask the assistant to print it
- Bash tool output (cat) may be collapsed in the UI
- User has to ask multiple times: "show me the full doc", "I still can't see it"
Expected behavior
Before asking for approval, the assistant should output the document content as direct text in the conversation (not via a tool call that gets collapsed). This way the user can read the full design doc and make an informed approval decision.
Suggested fix
In the Phase 5 (Design Doc) section of the office-hours SKILL.md, add an instruction after writing the document:
After writing the design doc to disk, output the full document content as direct text in the conversation (not via Bash cat or Read tool, which may be collapsed in the UI). Then present the AskUserQuestion for approval.
Environment
- Claude Code CLI (terminal)
- gstack office-hours skill
- Observed on macOS