Skill

research-brief

Turn a vague topic into an execution-ready research brief. Use when the user says "research this", "look into this", "what should we find out about", or provides an ambiguous topic that needs sharpening before subagents can work on it.

Install

npx claudepluginhub ildunari/kosta-plugins --plugin subagent-forge

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Build a compact but execution-ready research brief for the topic or decision the user provided.

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 30, 2026

Used By3 plugins

Actions

View Source View Plugin View on GitHub View README

Build a compact but execution-ready research brief for the topic or decision the user provided.

Sharpen the request without overcomplicating it.

What to produce

Return a structured brief with these sections:

Objective
- Restate the real question or decision.
Decision frame
- What choice is actually being made?
- What counts as a good answer?
Constraints and assumptions
- Explicit constraints from the request
- Reasonable assumptions you are making so work can start now
Search plan
- Broad-first search path
- Targeted follow-up path
- Official sources to prioritize
- Community or repo sources to verify against
Recommended worker lineup
- Which subagents from this plugin to use
- Which report mode each should use
- What each worker should answer
Deliverable shape
- What the final synthesis should contain
- What to exclude to keep it tight
Failure modes to watch
- Where this research could go wrong, stale, or fluffy

Rules

Keep it practical.
Do not ask clarifying questions unless the request is truly blocked.
Prefer strong assumptions over paralysis, but label them.
This skill prepares the work; it does not do the full research report itself.