gsd-research-phase

Analyzes project stage and produces actionable implementation recommendations for developers and managers, covering everything from workflows to finances and staffing in one place.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-research-phase-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-research-phase
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-research-phase
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-research-phase-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you investigate how to implement a specific development phase before committing to planning or implementation decisions.

Core Features & Use Cases

  • Phase validation against the roadmap: Confirms the requested phase exists and loads the correct phase metadata.
  • Context-aware research orchestration: Normalizes the phase input and gathers requirements, prior context, and state so the research starts from the right assumptions.
  • Dedicated researcher execution: Spawns a gsd-phase-researcher subagent and produces research output for reuse by the plan-phase workflow.

Use Case: You have completed a roadmap step and need a fresh, evidence-backed implementation approach for a given phase (for example, after planning changes or discovering new constraints).

Quick Start

Run the skill with the phase number you want to research, such as: "Research phase 3".

Frequently Asked Questions about gsd-research-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research implementation feasibility before committing to a development phase?

To research implementation feasibility, this Skill validates the phase against your roadmap, loads prior context and state, and orchestrates a dedicated researcher to output an evidence-backed approach for downstream planning.

What is phase research and when do I need it in a developer workflow?

Phase research investigates architectural choices before implementation. You need it after roadmap planning changes or when discovering new constraints, ensuring you validate feasibility before committing to a full plan.

How do I validate a development phase against a roadmap before planning?

Validating a phase requires confirming it exists in the roadmap and normalizing its input. The Skill loads the correct phase metadata, gathers requirements, and writes results to a phase-specific RESEARCH.md location.

Can I investigate architectural choices without generating a full implementation plan?

Yes, you can investigate architectural choices independently. The Skill spawns a researcher subagent to explore approaches and document findings, specifically delaying full plan generation for downstream consumption.

Does phase research require existing roadmap and state files to function?

Yes, phase research requires resolved paths for loading requirements, context, and state. It detects existing research and relies on normalized phase input from your roadmap to orchestrate the research correctly.

What is the best way to re-research a phase after planning changes?

The best way to re-research after planning changes is to run this Skill with the target phase number. It gathers fresh context, validates updated constraints, and overwrites the phase-specific RESEARCH.md output.