Agent skill

Gsd Research Phase

by SpillwaveSolutions in SpillwaveSolutions/agent-brain

Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)

MITAuto-check passedKnowledge Management

Install Gsd Research Phase

skills CLI
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install SpillwaveSolutions/agent-brain gsd-research-phase --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/gsd-research-phase .claude/skills/gsd-research-phase && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gsd-research-phase
GitHub stars
119
Token cost
~1.9k tokens
SKILL.md length
505 words
Files
1
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)

  • Works in 7 steps: Initialize Context → Validate Phase → Check Existing Research → …
  • Knowledge Management work in your project
  • SKILL.md covers A. Skill Invocation, B. AskUserQuestion →…, C. Task() → spawn_agent Mapping and 0. Initialize Context, plus 6 more sections
  • Calls node

What it does

Gsd Research Phase is an agent skill from SpillwaveSolutions/agent-brain. Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management. The repository describes itself as: Local-first RAG memory for AI agents: hybrid + GraphRAG search, MCP server with OAuth 2.1, plugin for Claude Code / OpenCode / Codex. The licence is MIT.

When your agent uses it

  • Knowledge Management work in your project

Example prompts

  • “/gsd-research-phase”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Initialize Context
  2. Validate Phase
  3. Check Existing Research
  4. Gather Phase Context
  5. Spawn gsd-phase-researcher Agent
  6. Handle Agent Return
  7. Spawn Continuation Agent

What it can do on your machine

Read from SKILL.md and the folder at commit 8339623. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gsd Research Phase loads about 1.9k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 505 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from SpillwaveSolutions/agent-brain at commit 8339623, republished under its MIT licence (© SpillwaveSolutions). 505 words, ~1,917 tokens.

Download SKILL.mdSave it as .claude/skills/gsd-research-phase/SKILL.md (or your agent's skills folder).
name
gsd-research-phase
description
Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)
metadata.short-description
Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-research-phase.
  • Treat all user text after $gsd-research-phase as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • header → header
  • question → question
  • Options formatted as "Label" — description → {label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y") → spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit (Codex uses per-role config, not inline model selection)
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<objective>
Research how to implement a phase. Spawns gsd-phase-researcher agent with phase context.

Note: This is a standalone research command. For most workflows, use $gsd-plan-phase which integrates research automatically.

Use this command when:

  • You want to research without planning yet
  • You want to re-research after planning is complete
  • You need to investigate before deciding if a phase is feasible

Orchestrator role: Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.

Why subagent: Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction. </objective>

<available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):

  • gsd-phase-researcher — Researches technical approaches for a phase </available_agent_types>
<context>
Phase number: {{GSD_ARGS}} (required)

Normalize phase input in step 1 before any directory lookups. </context>

<process>
Show full SKILL.md (167 more words)Show less

0. Initialize Context

bash
INIT=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" init phase-op "{{GSD_ARGS}}")
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi

Extract from init JSON: phase_dir, phase_number, phase_name, phase_found, commit_docs, has_research, state_path, requirements_path, context_path, research_path.

Resolve researcher model:

bash
RESEARCHER_MODEL=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" resolve-model gsd-phase-researcher --raw)

1. Validate Phase

bash
PHASE_INFO=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" roadmap get-phase "${phase_number}")

If found is false: Error and exit. If found is true: Extract phase_number, phase_name, goal from JSON.

2. Check Existing Research

bash
ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null

If exists: Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.

If doesn't exist: Continue.

3. Gather Phase Context

Use paths from INIT (do not inline file contents in orchestrator context):

  • requirements_path
  • context_path
  • state_path

Present summary with phase description and what files the researcher will load.

4. Spawn gsd-phase-researcher Agent

Research modes: ecosystem (default), feasibility, implementation, comparison.

markdown
<research_type>
Phase Research — investigating HOW to implement a specific phase well.
</research_type>

<key_insight>
The question is NOT "which library should I use?"

The question is: "What do I not know that I don't know?"

For this phase, discover:
- What's the established architecture pattern?
- What libraries form the standard stack?
- What problems do people commonly hit?
- What's SOTA vs what the agent's training thinks is SOTA?
- What should NOT be hand-rolled?
</key_insight>

<objective>
Research implementation approach for Phase {phase_number}: {phase_name}
Mode: ecosystem
</objective>

<files_to_read>
- {requirements_path} (Requirements)
- {context_path} (Phase context from discuss-phase, if exists)
- {state_path} (Prior project decisions and blockers)
</files_to_read>

<additional_context>
**Phase description:** {phase_description}
</additional_context>

<downstream_consumer>
Your RESEARCH.md will be loaded by `$gsd-plan-phase` which uses specific sections:
- `## Standard Stack` → Plans use these libraries
- `## Architecture Patterns` → Task structure follows these
- `## Don't Hand-Roll` → Tasks NEVER build custom solutions for listed problems
- `## Common Pitfalls` → Verification steps check for these
- `## Code Examples` → Task actions reference these patterns

Be prescriptive, not exploratory. "Use X" not "Consider X or Y."
</downstream_consumer>

<quality_gate>
Before declaring complete, verify:
- [ ] All domains investigated (not just some)
- [ ] Negative claims verified with official docs
- [ ] Multiple sources for critical claims
- [ ] Confidence levels assigned honestly
- [ ] Section names match what plan-phase expects
</quality_gate>

<output>
Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
</output>
Task(
  prompt=filled_prompt,
  subagent_type="gsd-phase-researcher",
  model="{researcher_model}",
  description="Research Phase {phase}"
)

5. Handle Agent Return

## RESEARCH COMPLETE: Display summary, offer: Plan phase, Dig deeper, Review full, Done.

## CHECKPOINT REACHED: Present to user, get response, spawn continuation.

## RESEARCH INCONCLUSIVE: Show what was attempted, offer: Add context, Try different mode, Manual.

6. Spawn Continuation Agent

markdown
<objective>
Continue research for Phase {phase_number}: {phase_name}
</objective>

<prior_state>
<files_to_read>
- .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md (Existing research)
</files_to_read>
</prior_state>

<checkpoint_response>
**Type:** {checkpoint_type}
**Response:** {user_response}
</checkpoint_response>
Task(
  prompt=continuation_prompt,
  subagent_type="gsd-phase-researcher",
  model="{researcher_model}",
  description="Continue research Phase {phase}"
)
</process>

<success_criteria>

  • Phase validated against roadmap
  • Existing research checked
  • gsd-phase-researcher spawned with context
  • Checkpoints handled correctly
  • User knows next steps </success_criteria>

© SpillwaveSolutions, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/gsd-research-phase of SpillwaveSolutions/agent-brain.

Open the folder on GitHubat commit 8339623

Compare with similar skills

Gsd Research Phase next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gsd Research Phase compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gsd Research Phase this skillSpillwaveSolutions/agent-brain119—~1.9kAutomated safety check: PassMIT
Logseq Review Workflow Evallogseq/logseq45k—~1kAutomated safety check: PassAGPL-3.0
Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill2.5k2 repos~3.2kAutomated safety check: PassNone
Obsidian CLIAtmosphere/atmosphere3.8k13 repos~795Automated safety check: PassApache-2.0
Esm Cjs Risk Scanlogseq/logseq45k—~3.3kAutomated safety check: PassAGPL-3.0
Capture Conversationoutline/outline41k—~474Automated safety check: PassCustom licence

Similar skills

  • Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…

    45k GitHub stars~1k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Baoyu URL To Markdown

    sdyckjq-lab/llm-wiki-skill

    Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.

    2.5k GitHub starsUsed in 2 repos~3.2k tokens
    Knowledge ManagementAuto-check passed
  • Obsidian CLI

    Atmosphere/atmosphere

    Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.

    3.8k GitHub starsUsed in 13 repos~795 tokens
    Knowledge ManagementAuto-check passed
  • Esm Cjs Risk Scan

    logseq/logseq

    Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.

    45k GitHub stars~3.3k tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Capture Conversation

    outline/outline

    Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.

    41k GitHub stars~474 tokensUpdated today
    Knowledge ManagementAuto-check passed
  • Karpathy LLM Wiki

    Astro-Han/karpathy-llm-wiki

    A skill your agent uses when building or maintaining a personal LLM-powered knowledge base.

    2.4k GitHub stars~3.6k tokensUpdated 2 mo ago
    Knowledge ManagementAuto-check passed

More from SpillwaveSolutions/agent-brain

All 55 skills in this repo
  • Gsd Complete Milestone

    SpillwaveSolutions/agent-brain

    Archive completed milestone and prepare for next version. An agent skill from SpillwaveSolutions/agent-brain.

    119 GitHub starsUsed in 4 repos~1.6k tokens
    Auto-check passed
  • Mastering Python Skill

    SpillwaveSolutions/agent-brain

    Modern Python coaching covering language foundations through advanced production patterns.

    119 GitHub stars~1.4k tokensUpdated 19 days ago
    Auto-check: notes
  • Gsd Debug

    SpillwaveSolutions/agent-brain

    Systematic debugging with persistent state across context resets

    119 GitHub starsUsed in 4 repos~1.5k tokens
    Auto-check passed
  • Gsd Review Backlog

    SpillwaveSolutions/agent-brain

    Review and promote backlog items to active milestone. An agent skill from SpillwaveSolutions/agent-brain.

    119 GitHub starsUsed in 3 repos~961 tokens
    Auto-check passed
  • Configuring Agent Brain

    SpillwaveSolutions/agent-brain

    Installation and configuration skill for Agent Brain document search system.

    119 GitHub stars~7k tokensUpdated 19 days ago
    Auto-check: notes
  • Gsd Thread

    SpillwaveSolutions/agent-brain

    Manage persistent context threads for cross-session work. An agent skill from SpillwaveSolutions/agent-brain.

    119 GitHub starsUsed in 3 repos~1.2k tokens
    Auto-check passed

Questions about Gsd Research Phase

What does Gsd Research Phase do?

Research how to implement a phase (standalone - usually use $gsd-plan-phase instead). Gsd Research Phase is an agent skill from SpillwaveSolutions/agent-brain.

When should I use Gsd Research Phase?

Gsd Research Phase fits situations like: knowledge Management work in your project.

How do I install Gsd Research Phase in Claude Code?

Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a claude-code`. Or copy the skill folder (.codex/skills/gsd-research-phase in SpillwaveSolutions/agent-brain) into .claude/skills/gsd-research-phase in your project. Claude Code loads it when a task matches its description.

How do I install Gsd Research Phase in Codex?

Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a codex`. Or copy the skill folder (.codex/skills/gsd-research-phase in SpillwaveSolutions/agent-brain) into .agents/skills/gsd-research-phase in your project. Codex loads it when a task matches its description.

Can I use Gsd Research Phase in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gsd-research-phase, .gemini/skills/gsd-research-phase, .github/skills/gsd-research-phase and .opencode/skills/gsd-research-phase in your project.

What does Gsd Research Phase need to run?

Going by SKILL.md and its folder, Gsd Research Phase needs the command-line tools its instructions call (node).

Does Gsd Research Phase access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gsd Research Phase safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gsd Research Phase use?

Gsd Research Phase is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gsd Research Phase use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gsd Research Phase?

Skills that share tags, products or a category with Gsd Research Phase: Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Esm Cjs Risk Scan (logseq/logseq, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gsd Research Phase?

SpillwaveSolutions (a GitHub organization) maintains it in SpillwaveSolutions/agent-brain, which has 119 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 19, 2026.

Source: SpillwaveSolutions/agent-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.