research
Originally fromsamhvw8/dot-claude
Installation
SKILL.md
Technical Research
Conduct evidence-driven technical research. Default output is a Formal Report (Path A) — a persistent artifact with evidence files. Other paths require explicit user signals:
- Path A — Formal Report (DEFAULT): Persistent artifact in the resolved reports directory with evidence files. This is the default unless the user explicitly opts out.
- Path B — Direct Answer: Findings delivered in conversation only. Requires explicit user request (e.g., "just tell me", "no report needed", "quick answer").
- Path C — Update Existing Report: Surgical additions/corrections to an existing report. Triggered when the user references an existing report or says "update/refresh/extend."
Autonomy Mode
Research supports two execution modes:
| Mode | Behavior | How entered |
|---|---|---|
| Supervised (default) | Pause at scoping gate for user rubric confirmation; present routing options interactively | Default when invoked by a user in an interactive session |
| Headless | Auto-confirm rubric after proposing it; auto-select routing decisions; skip interactive follow-up prompts. All other quality gates (worldmodel + routing, validation, evidence standards) remain enforced. | $ARGUMENTS includes --headless, OR container environment detected (/.dockerenv exists or CONTAINER=true), OR invoked via -p non-interactive mode |
--fanout |
At Step 3 or Step 6, use nested fanout whenever the routing heuristic says it's warranted. At Step 3: if rubric has 5+ P0/Deep independent dimensions, fanout replaces standard research. At Step 6: auto-select all follow-ups assessed as "heavy." Lighter items handled by subagents. Requires --headless. |
$ARGUMENTS includes --fanout (must also include --headless) |