Researching
- 1 installs
- 19 repo stars
- Updated March 1, 2026
- haowjy/orchestrate
Explores a codebase, evaluates 2-3 approaches, and recommends one with reasoning tied to the specific project before planning.
About
Investigates a problem space by reading project instructions, searching existing patterns, and comparing alternatives with pros and cons specific to the codebase. A developer uses it to gather context and produce a recommendation report before starting a plan.
- Evaluates 2-3 approaches with codebase-specific pros and cons
- Outputs a structured report with problem statement, context, and recommendation
Researching by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,476 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/haowjy/orchestrate --skill researchingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 19 |
| Last updated | March 1, 2026 |
| Repository | haowjy/orchestrate ↗ |
What it does
Explores a codebase, evaluates 2-3 approaches, and recommends one with reasoning tied to the specific project before planning.
Files
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
# Runtime artifacts — hidden directories are generated, never committed
.*
!.gitignore
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k