office-hours: design doc not visible to user when AskUserQuestion requests approval

Open Beginner friendly
#879 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
markdown
Domain
cli, developer-experience

Research direction

Start in the Phase 5 (Design Doc) section of office-hours/SKILL.md and inspect the steps after the design document is written and before AskUserQuestion requests approval. Update the instructions so the full document is shown as direct conversation text, then manually exercise the office-hours flow to confirm the document appears before the approval prompt.

Written by the indexing model from the issue text.

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

  1. Design doc is written to ~/.gstack/projects/{slug}/
  2. AskUserQuestion asks "Approve / Revise / Start over"
  3. User cannot see the document — they have to ask the assistant to print it
  4. Bash tool output (cat) may be collapsed in the UI
  5. 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
Dominant language
TypeScript
Stars
134k
Forks
19.9k
Avg merge
20h 59m
Merged PRs (30d)
21

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from garrytan/gstack

All issues in garrytan/gstack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.