Explicit-only interview loop for stress-testing a plan, decision, or idea. Use only when the user asks to grill, interrogate, interview, or stress-test their thinking before action.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Interview the user relentlessly until you reach a shared understanding. Map this as a design tree: every decision branches into the decisions that hang off it.
Work the tree in rounds. The frontier is every decision whose prerequisites are already settled: the questions you can ask now without guessing at answers you haven't heard yet. Ask at most three independent, high-value frontier questions about material unresolved decisions in one round. Prefer a usable structured-question tool when available; otherwise ask concise numbered questions. Give your recommended answer. Then wait for the user's answers before the next round.
Format a round like so:
❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
---
❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
➡️ <your recommended answer>
Word each question so "yes" accepts your recommended answer.
Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a later round, not this one.
Finding facts is your job, never the user's. Discover repository and environment facts before asking questions, using available tools directly. The decisions are the user's: put each to them and wait.
The session is done when no material unresolved decision remains. Respect choices already settled by the user or authoritative evidence; do not exhaust speculative branches. End by reporting the shared understanding and open decisions. Do not implement automatically; implementation requires a separate user request.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.
日本語の概要は準備中です。原文の説明を表示しています。
Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.
日本語の概要は準備中です。原文の説明を表示しています。
Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.
日本語の概要は準備中です。原文の説明を表示しています。
Build and sharpen a project's domain model. Use only when actively changing glossary or ubiquitous-language terms, or recording a durable architectural decision; merely reading a glossary is not a trigger.
日本語の概要は準備中です。原文の説明を表示しています。
Explicit-only workflow that writes a redacted continuation handoff to a unique temporary Markdown file. Use only when the user explicitly asks for a handoff for another session.
日本語の概要は準備中です。原文の説明を表示しています。