Skip to content

Add issue #143 report: AskUserQuestion PAI Q&A pattern design#149

Merged
virtualian merged 1 commit intomainfrom
issue-143-askuserquestion-investigation
Apr 21, 2026
Merged

Add issue #143 report: AskUserQuestion PAI Q&A pattern design#149
virtualian merged 1 commit intomainfrom
issue-143-askuserquestion-investigation

Conversation

@virtualian
Copy link
Copy Markdown
Owner

Summary

  • Investigation-only deliverable for Investigate: AskUserQuestion-equivalent Q&A pattern for PAI (not just Claude Code) #143 (issue body explicitly excludes implementation).
  • Recommends hybrid design: keep direct AskUserQuestion calls in CC; add PAI-level ENUMERATE→OFFER trigger gate for ALGORITHM mode; add ❓ OPEN_CHOICES: output field for NATIVE mode; subagent-bubble protocol via pending_user_choices[]; abstract Request/Response contract for non-CC harnesses.
  • 13 coupling points verified across $PAI_DIR runtime and Packs/. In-session runtime probe confirmed general-purpose subagents have neither AskUserQuestion nor ToolSearch in their surface (ASK_USER_QUESTION_STATUS: ABSENT).

Report structure

§1 Executive Summary · §2 Problem Statement · §3 Current State (13 coupling points) · §4 Design Decisions (4 sub-decisions × 4 options each) · §5 Inventory (10 touchpoints) · §6 Trade-offs Summary · §7 Recommendation · §8 Implementation Handoff (7 work items) · §9 Scope Boundary · Appendix A (caveats) · Appendix B (related existing work).

Test plan

  • Review report at reports/20260421-issue-143-askuserquestion-pai-design.md
  • Confirm the Hybrid (§4.1c), Combined+OPEN_CHOICES (§4.2c+d), Bubble (§4.3b), Abstract Contract (§4.4b) recommendation aligns with PAI conventions
  • Confirm §8 handoff items are tractable for a single-author implementation PR (~1 engineering day)
  • Sanity-check the 13-row coupling table matches the current runtime and Packs/

Scope

  • No PAI runtime code changes
  • No prompt file edits (Algorithm, AISTEERINGRULES, CLAUDE.md, SKILL.md, etc. all untouched)
  • No hook changes (SetQuestionTab / QuestionAnswered untouched)
  • Report file is the sole addition

Closes #143.
Follow-up implementation tracked in #148.

Investigation-only deliverable. Recommends hybrid design:
keep direct AskUserQuestion calls in CC, add PAI-level
ENUMERATE→OFFER trigger gate for ALGORITHM + OPEN_CHOICES
output field for NATIVE, subagent-bubble protocol via
pending_user_choices[], and abstract response contract for
non-CC harnesses. 13 coupling points verified across runtime
and Packs. Runtime probe confirms general-purpose subagents
lack direct AskUserQuestion access. Implementation is
out-of-scope; §8 lists 7 work items for a follow-up issue.
@virtualian virtualian merged commit b955fa6 into main Apr 21, 2026
@virtualian virtualian deleted the issue-143-askuserquestion-investigation branch April 21, 2026 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Investigate: AskUserQuestion-equivalent Q&A pattern for PAI (not just Claude Code)

1 participant