| name | research |
| description | Force explicit research mode — Scope → Discover → Synthesize → Plan — with the approval gate before any implementation. |
| user-invocable | true |
| disable-model-invocation | true |
/research
The user invoked /research with: $ARGUMENTS
Procedure:
- Ensure
core-research is activated for this session. If you can't recall its workflow from earlier, re-activate via ActivateSkill('core-research') — silent and auto-approved. It provides the canonical Scope → Discover → Synthesize → Plan workflow and the approval gate.
- Treat the user's input as the research question. If the question is ambiguous or under-specified, complete the Scope step by asking once before discovering.
- Apply the workflow. Do not modify code during Scope or Discovery. When running interactively, do not begin implementation until the user has explicitly approved the plan — this overrides the Working Loop's Frame step, which would otherwise work autonomously on directives. When running non-interactively (no user to approve), present the plan inline and then proceed.
- Deliver per the workflow's output standards: direct answer (for questions), Action → Target → Verification steps (for plans), or compared options with rationale (for decisions). Cite sources:
file:line for code, URLs for web.
