haowjy/orchestrate · Archived

researching

Explores codebases and evaluates approaches before planning. Use when investigating a problem space, comparing alternatives, or gathering context for a plan.

First seen Jun 4, 2026

Installation

$ npx skills add haowjy/orchestrate --skill researching

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from haowjy/orchestrate.

npx skills add haowjy/orchestrate

Browse all from haowjy/orchestrate

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 19
License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,319 B
  • docs SUMMARY.md 176 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Research

Explore the codebase, research best practices, evaluate alternatives, and recommend the best solution with clear reasoning.

Key Constraints

  • Read project instructions first — CLAUDE.md or AGENTS.md at 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