Researching
Explores codebases and evaluates approaches before planning. Use when investigating a problem space, comparing alternatives, or gathering context for a plan.From its SKILL.md
npx -y skills add haowjy/orchestrate --skill researchingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, as published. Nobody here has run it
Research
Explore the codebase, research best practices, evaluate alternatives, and recommend the best solution with clear reasoning.
Key Constraints
- Read project instructions first —
CLAUDE.mdorAGENTS.mdat repo root, plus stack-specific files. - Search before suggesting — check if something already exists before recommending new implementations.
- Evaluate 2-3 approaches — describe each, compare pros/cons specific to this codebase, and recommend one.
- Justify with WHY — every recommendation needs reasoning tied to the specific codebase, not generic advice.
- Be specific — include file paths, function names, line numbers. Vague findings aren't useful.
Output
Produce a report with these sections:
- Problem Statement
- Codebase Context — existing patterns, utilities, integration points (with file paths)
- Best Practices — industry recommendations with sources
- Alternative Approaches — 2-3 approaches with description, pros, cons, codebase fit
- Recommendation — which approach and WHY it fits this codebase
- Open Questions