/guided-research
Deep research at the moments that actually justify it.
What it does
An orchestration layer over deep research that decides when the expensive version is worth running — architectural decisions, new problem domains with established best practice, unfamiliar APIs you have already failed against twice — then organizes what comes back so it is reusable rather than read once.
When to reach for it
Before choosing a library, framework, or structural approach. Agents systematically under-research at exactly these moments: two shallow web searches at a decision point is the signal.
It's working if
- It sometimes concludes the question does not need the expensive version, and stops there.
- You open the write-up again a month later instead of re-running the research.
- You can name what you rejected and why, not just what you chose.
Install this skill
Then type /guided-research in your agent.
npx skills@latest add smorinlabs/smorinlabs-harness -s guided-researchOr install it as the guided-research plugin.
/plugin install guided-research@smorinlabs-harnessWhere it fits
- /factor-architect — consumes the research when the decision is architectural.
- /project-refine — the caller, when scoping turns up something nobody knows.