Skip to content
Development
Command

/research

On-demand domain research — evaluate technology options, investigate ecosystem choices

From plugin
6625 skills20 agents25 commands4 hooks
shell
$ npx -y skills add lgbarn/shipyard --agent claude-code

Ships with shipyard. Installing the plugin gets this command.

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/research

Context preview

What this command does when you run it.

On-demand domain research — evaluate technology options, investigate ecosystem choices

Command definition

research.md
description: "On-demand domain research — evaluate technology options, investigate ecosystem choices"
disable-model-invocation: true
argument-hint: "<topic> — required: technology choice, domain question, or ecosystem investigation"

/shipyard:research - On-Demand Domain Research

You are executing on-demand domain research. Follow these steps precisely.

<prerequisites>

Step 1: Parse Arguments

Extract from the command:

  • `topic` (REQUIRED): The research topic. Examples:
  • `"React vs Vue for dashboard"` — technology comparison
  • `"best Postgres connection pooling library"` — ecosystem investigation
  • `"authentication approaches for REST API"` — architectural research
  • `"gRPC vs REST for microservices"` — protocol comparison

If no topic is provided, ask the user what they want to research.

Step 2: Detect Context

1. Check if `.shipyard/` exists (optional — this command works anywhere). 2. If `.shipyard/config.json` exists, read `model_routing.planning` for model selection. 3. Otherwise, use default model: **sonnet**. 4. Follow **Worktree Protocol** (see `docs/PROTOCOLS.md`) — detect worktree context.

</prerequisites>

<execution>

Step 3: Build Agent Context

Assemble context per **Agent Context Protocol** (see `docs/PROTOCOLS.md`):

  • The research topic from Step 1
  • `.shipyard/PROJECT.md` (if exists) — for project stack context
  • Codebase docs per **Codebase Docs Protocol** (if `.shipyard/` exists) — especially STACK.md, ARCHITECTURE.md
  • Working directory and current branch
  • Any existing technology choices to consider compatibility with

Step 4: Dispatch Researcher

Dispatch a **researcher agent** (subagent_type: "shipyard:researcher") with:

  • Follow **Model Routing Protocol** — resolve model from `model_routing.planning` (default: sonnet)
  • max_turns: 15
  • All context from Step 3
  • Instruction: Investigate the topic thoroughly — identify candidates, deep-dive each via web search and documentation, analyze codebase compatibility, build comparison matrix, formulate recommendation with risks and mitigations

</execution>

<output>

Step 5: Present Results

Display the research document to the user.

Offer follow-up: > "Would you like me to: > - Save this research to `.shipyard/` for future reference > - Create an implementation plan based on the recommendation > - Research a related topic"

</output>

Read more
Read it on GitHub ↗
Ships withshipyard

A Claude Code plugin for structured project execution. Plan work in phases, build with parallel agents and TDD, review with security audits and quality gates, and ship with confidence.

Get the whole plugin, auto-invoked
Stats
66
Stars
0
Views
3
Forks
Active
Maintenance
Shell
Language
MIT
License
19d ago
Last commit
6mo ago
Created

Repo: lgbarn/shipyard