メニュー
Ask the user a structured, multiple-choice question (tool ask_user_question) instead of guessing when a decision is genuinely the user's to make. Tabbed single/multi-select dialog with previews and an "Other" free-text fallback.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
SDD-mode PR-boundary review policy for Pi. The root launches visible reviewer lanes, publishes triage, ends the turn for acknowledgement, then fixes in a separate follow-up. Review is independent of CI.
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
Create a pull request with review, REQ backlinks, push, and CI handoff.
Verify a deployed UI in a browser for interaction, mobile layout, and visuals.
Workflow for /sdd clean — rescuing a rotted spec. Mode-aware behaviors (interactive/auto/unleashed), safety nets, what gets cleaned (incl. per-AC @impl AND @test anchor backfill at parity, gated by enforce_tdd), JUDGMENT auto-resolution rules. Invoked when /sdd clean runs. Requires the spec-driven-development skill for REQ format and Status semantics, and the spec-enforce skill family for the detection mechanics.
| name | rpiv-ask-user-question |
| description | Ask the user a structured, multiple-choice question (tool ask_user_question) instead of guessing when a decision is genuinely the user's to make. Tabbed single/multi-select dialog with previews and an "Other" free-text fallback. |
| disable-model-invocation | true |
Provides the ask_user_question tool: present one or more structured questions, each with 2+ typed options, optional multiSelect, optional per-option preview, and an automatic free-text "Other" fallback. Returns the user's selection(s) plus any notes.
Use it only when a decision is genuinely the user's to make and you cannot resolve it from the request, the code, or sensible defaults — and the answer changes what you do next:
ask_user_question with 1–4 questions; each question has a short header chip and 2–4 options with a label + description. Put your recommended option first and mark it (Recommended). Use multiSelect: true only when choices are not mutually exclusive. Use preview to show side-by-side artifacts (mockups, code snippets) the user must compare.
