research-quick-answer

name

research-quick-answer

description

Answer one or more focused factual research questions with source citations and return inline — no persisted research document. Dispatches the six read-only research children (codebase-locator, codebase-analyzer, codebase-pattern-finder, thoughts-locator, thoughts-analyzer, web-search-researcher) per question shape, in parallel, across the hide-the-intent boundary. Per-question synthesis: each answer carries file:line / URL / thoughts-alias citations, a confidence level, and an explicit gap note when evidence is thin. Mode-aware: interactive when a user invokes it (clarifies vague questions via the question tool); autonomous when dispatched from a workflow (emits ERROR on malformed dispatch, CLARIFICATION_NEEDED when a question is too vague to compose a child prompt). The fast path for freshness checks, existence checks, and grilling-loop research batches.

Execute workflow by following instructions and producing output Always read COMPLETE files - NEVER use offset/limit when reading any workflow related files Instructions are MANDATORY - either as file path, steps or embedded list in YAML, XML or markdown Execute ALL steps in instructions IN EXACT ORDER Save to template output file after EVERY "template-output" tag NEVER skip a step - YOU are responsible for every step's execution without fail or excuse Steps execute in exact numerical order (1, 2, 3...) unless an explicit goto directs otherwise Optional steps: Ask user unless YOLO mode active Template-output tags: Save content, discuss with the user the section completed, and NEVER proceed until the user indicates to proceed (unless YOLO mode has been activated) For each step in instructions:

  <substep n="1a" title="Track Progress">
    <action if="first iteration">Create todo list from all instruction step titles (TodoWrite)</action>
    <action>Mark current step as in_progress (TodoWrite)</action>
  </substep>

  <substep n="1b" title="Handle Step Attributes">
    <check>If optional="true" and NOT YOLO -> Use Question tool to ask user whether to include (Yes/Skip)</check>
    <check>If if="condition" -> Evaluate condition</check>
    <check>If for-each="item" -> Repeat step for each item</check>
    <check>If repeat="n" -> Repeat step n times</check>
  </substep>

  <substep n="1c" title="Execute Step Content">
    <action>Process step instructions (markdown or XML tags)</action>
    <action>Replace {{variables}} with values (ask user if unknown)</action>
    <execute-tags>
      <tag>action -> Perform the action</tag>
      <tag>action type="script" -> Execute as shell command, capture output</tag>
      <tag>check if="condition" -> Conditional block wrapping actions (requires closing &lt;/check&gt;)</tag>
      <tag>ask -> Prompt user using Question tool and WAIT for response. When options exist, present them as selectable choices. For open-ended questions, provide helpful suggested options with custom input enabled</tag>
      <tag>invoke-skill name="skill-name" -> Execute another skill via OpenCode skill system</tag>
      <tag>invoke-agent name="subagent" prompt="task" -> Delegate to subagent via Task tool</tag>
      <tag>goto step="x" -> Jump to specified step (used for explicit loop-back in Q-R style flows)</tag>
    </execute-tags>
  </substep>

  <substep n="1d" title="Handle template-output Tags">
    <if tag="template-output">
      <mandate>Generate content for this section</mandate>
      <mandate>Save to file (Write first time, Edit subsequent)</mandate>
      <action>Display generated content</action>
      <action>Use Question tool to present checkpoint options. WAIT for response.
        <options>
          <option label="Continue" description="Approve this section and move to the next step" />
          <option label="Advanced Elicitation" description="Explore this section deeper before proceeding" />
          <option label="YOLO" description="Auto-complete the rest of this workflow without stopping" />
        </options>
        <if response="Advanced Elicitation">
          <action>Invoke advanced-elicitation skill</action>
        </if>
        <if response="Continue">
          <action>Continue to next step</action>
        </if>
        <if response="YOLO">
          <action>Enter YOLO mode for the rest of the workflow</action>
        </if>
      </action>
    </if>
  </substep>

  <substep n="1e" title="Step Completion">
    <action>Mark current step as completed (TodoWrite)</action>
    <check>If no special tags and NOT YOLO:</check>
    <action>Use Question tool to ask:
      <options>
        <option label="Continue" description="Proceed to the next step" />
        <option label="Edit" description="Revise this step before moving on" />
      </options>
    </action>
  </substep>
</step>

<step n="2" title="Completion">
  <check>Confirm all instruction steps have been executed</check>
  <output>Workflow complete.</output>
</step>

Full user interaction and confirmation of EVERY step at EVERY template output - NO EXCEPTIONS except YOLO mode Skip all confirmations and elicitation, minimize prompts and try to produce all of the workflow automatically by simulating the remaining discussions with a simulated expert user step n="X" goal="..." - Define step with number and goal substep n="Xa" title="..." - Sub-step within a step phase n="X" - Phase within a substep optional="true" - Step can be skipped if="condition" - Conditional execution for-each="collection" - Iterate over items repeat="n" - Repeat n times action - Required action to perform action type="script" - Execute shell command action if="condition" - Single conditional action (inline, no closing tag needed) check if="condition">...</check> - Conditional block wrapping multiple items (closing tag required) ask - Get user input via Question tool (ALWAYS wait for response before continuing). Present defined options as selectable choices. For open-ended questions, offer helpful suggestions with custom input enabled goto - Jump to another step (explicit loop-back) invoke-skill - Call another skill invoke-agent - Delegate to subagent via Task tool invoke-protocol - Execute a reusable protocol (e.g., discover_inputs) template-output - Save content checkpoint critical - Cannot be skipped example - Show example output note - Informational content output - Display to user without saving halt-conditions - Define conditions that MUST stop execution condition - Single halt condition validation - Pre-condition rules to check - This is the complete workflow execution engine - You MUST follow instructions exactly as written - This workflow uses INTENT-DRIVEN PLANNING - adapt organically to product type and context - YOU ARE FACILITATING A CONVERSATION with a user to produce a final document step by step - The whole process is meant to be collaborative - helping the user flesh out their ideas - Do not rush or optimize and skip any section Answer one or more focused factual questions and return the answers inline with citations. Dispatch the right research child per question shape; synthesize per question; never persist a research document — the fast path for lookups, freshness checks, and grilling-loop research batches.

<inputs>
  Interactive (user invokes [QA]):
  - One or more questions in natural language; scope and output shape
    elicited if the question is too vague to dispatch.

  Autonomous (dispatched from a workflow):
  - questions: array of entries, each with
    - question_text (required)
    - scope (optional; directory globs, file paths, or domain)
    - child_subagent_hint (optional; overrides shape inference)
    - expected_output_shape (required)
  - web_search_approved (boolean; required true for any question
    that routes to web-search-researcher)
</inputs>

<outputs>
  Inline synthesis only — no persisted document. Per question:
  answer with citations, confidence level, and gap note. Autonomous
  mode returns a structured signal (SUCCESS / ERROR /
  CLARIFICATION_NEEDED).
</outputs>

<key-discipline>
  Hide-the-intent: every child prompt carries the question alone —
  never the parent task's intent.

  Silence is data: "searched X, Y, Z; no matches" is a finding, not
  a failure. A negative finding ships as a cited answer.

  No persistence: if a lookup turns out to be load-bearing, the
  caller escalates to [FS] Focused Study or [CI] Comprehensive
  Investigation, which persist.
</key-discipline>

<step n="1" title="Orient">
  <action>Load and execute: references/steps/step-01-orient.xml</action>
</step>

<step n="2" title="Plan Dispatch">
  <action>Load and execute: references/steps/step-02-plan-dispatch.xml</action>
</step>

<step n="3" title="Dispatch and Synthesize">
  <action>Load and execute: references/steps/step-03-dispatch-synthesize.xml</action>
</step>

<step n="4" title="Return">
  <action>Load and execute: references/steps/step-04-return.xml</action>
</step>

After step 4 returns the synthesis, the lookup is complete. In interactive mode, offer a follow-up question or escalation to a persisting capability. In autonomous mode, the structured signal is the final return to the dispatching caller.