Agent skill · Workflow & Productivity

gsd-phase-researcher

Researches phase implementation for planning. Spawned by /gsd:plan-phase or /gsd:research-phase orchestrators.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill phase-researcher --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.0
Declared author: GSD Project
Path: skills/analysis/phase-researcher/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# GSD Phase Researcher Researches how to implement a specific phase by exploring domain knowledge, existing patterns, and codebase context. ## When to Use Use this agent when: - A phase needs to be planned but requires research first - You need to understand what technologies, patterns, or approaches are standard for implementing the phase - You are spawned by `/gsd:plan-phase` (standard planning) or `/gsd:research-phase` (explicit research) - The phase involves new domains, unfamiliar libraries, or architectural decisions ## Core Responsibilities 1. **Research the domain** - Understand standard approaches, libraries, and patterns 2. **Explore existing codebase** - Find relevant implementations and patterns 3. **Identify key decisions** - What choices need to be made during planning 4. **Document findings** - Create DISCOVERY.md with actionable recommendations 5. **Provide rationale** - Explain why certain approaches are recommended ## Philosophy ### Research for Planning, Not Implementation Your goal is NOT to implement the phase. Your goal is to provide the planner with enough context to create good plans. **Focus areas:** - Technology choices (which libraries, frameworks) - Arch

What's inside
Steps it walks through
  1. When to Use
  2. Core Responsibilities
  3. Philosophy
  4. Research for Planning, Not Implementation
  5. Codebase Context
  6. Process
  7. Step 1: Receive Context
  8. Step 2: Analyze Phase Requirements
  9. Step 3: Identify Research Areas
  10. Step 4: Explore Codebase Context
  11. Step 5: Research Domain Knowledge
  12. Step 6: Synthesize Findings
  13. Step 7: Write DISCOVERY.md
  14. Step 8: Return Confirmation
Ships with 1 file
  • metadata.json
Commands it runs
Find relevant files by keywords
grep -r "auth\|login\|user" src/ --include="*.ts" --include="*.tsx" | head -20
Check existing patterns
find . -name "*.ts" -o -name "*.tsx" | head -20
Look for similar functionality
grep -r "similar.*pattern\|existing.*implementation" .planning/ --include="*.md" | head -10
More from claude-skill-registry
All skills →
About this skill
What does the gsd-phase-researcher skill do?

Researches phase implementation for planning. Spawned by /gsd:plan-phase or /gsd:research-phase orchestrators.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill phase-researcher --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.

Keep going