plan-research
Research a problem space with evidence gathering and source validation.
npx skills add majiayu000/claude-skill-registry --skill plan-research-daemn256-workspace-repo-templ --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Plan Research The Planner drives this workflow. Investigate a problem space by gathering evidence from the codebase, documentation, and external sources. Produce a structured research summary with cited sources. --- ## Phase 1: Scope the Investigation Define the boundaries before researching. ### Steps 1. State the research question clearly 2. Identify what you need to learn and why 3. Define what is in-scope and out-of-scope 4. List known starting points (files, docs, APIs, prior ADRs) ### Output Produce a scoped research brief covering: research question, in/out scope, starting points. **Approval Required:** No --- ## Phase 2: Gather Evidence Collect evidence from internal and external sources. ### Internal Sources 1. Search the codebase for relevant patterns, implementations, and conventions 2. Read existing ADRs, architecture docs, and design notes 3. Review git history for context on past decisions 4. Quantify where possible (line counts, file counts, dependency counts) ### External Sources 1. Use `WebFetch` to read official documentation, changelogs, or specifications 2. Use `mcp__github__search_repositories` to explore prior art in open source 3. Do NOT rely solely on trai
- Phase 1: Scope the Investigation
- Steps
- Output
- Phase 2: Gather Evidence
- Internal Sources
- External Sources
- Evidence Standards
- Phase 3: Synthesize
- ⛔ CHECKPOINT
- Error Handling
What does the plan-research skill do?
Research a problem space with evidence gathering and source validation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill plan-research-daemn256-workspace-repo-templ --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.