/research
Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing.
> /plugin marketplace add nWave-ai/nWave > /plugin install nw@nwave-marketplace
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.
Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing.
Command definition
research.mddescription: "Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing."
argument-hint: '[topic] - Optional: --research_depth=[overview|detailed|comprehensive|deep-dive] --skill-for=[agent-name]'
NW-RESEARCH: Evidence-Driven Knowledge Research
**Wave**: CROSS_WAVE **Agent**: Nova (nw-researcher) **Command**: `*research`
Overview
Systematic evidence-based research with source verification. Cross-wave support providing research-backed insights for any nWave phase using trusted academic|official|industry sources.
Optional `--skill-for={agent-name}` distills research into a practitioner-focused skill file for a specific agent.
Orchestration: Trusted Source Config
At orchestration time, before invoking the researcher subagent:
1. **Read** `.nwave/trusted-source-domains.yaml` from the project root 2. **If file missing**, seed it from the defaults in the `## Default Trusted Sources` section below, then notify the user: "Seeded `.nwave/trusted-source-domains.yaml` with defaults (7 categories, 42 trusted domains, 5 excluded). Edit the YAML directly to customize." 3. **Embed** the YAML content inline in the researcher subagent Task prompt so the agent receives trusted source config via prompt context
Agent Invocation
@nw-researcher
Execute \*research on {topic} [--skill-for={agent-name}].
**Configuration:**
- research_depth: detailed # overview/detailed/comprehensive/deep-dive
- source_preferences: ["academic", "official", "technical_docs"]
- output_directory: docs/research/
- skill_for: {agent-name} # Optional: distilled skill for specified agent
- skill_output_directory: ~/.claude/nWave/skills/{agent-name}/
Output Management
The researcher MUST create the output file in the FIRST 5 turns with a document skeleton (title, sections, placeholders). All subsequent findings are written DIRECTLY to this file as they are gathered -- never held only in context.
If the agent is interrupted or runs out of turns, the output file contains all work done so far. This is the researcher's equivalent of the crafter's "commit early, commit often."
Progressive write checkpoints:
- Turn ~5: Output file exists with skeleton
- Turn ~10: First findings written
- Turn ~25: All gathered findings written so far
- Turn ~35: Stop gathering, begin synthesizing
- Turn ~45+: Polish only
Progress Tracking
The invoked agent MUST create a task list from its workflow phases at the start of execution using TaskCreate. Each phase becomes a task with the gate condition as completion criterion. Mark tasks in_progress when starting each phase and completed when the gate passes. This gives the user real-time visibility into progress.
Success Criteria
**Research:**
- [ ] All sources from trusted source domains from prompt context
- [ ] Cross-reference performed (3+ sources per major claim ideal, 2 acceptable, 1 authoritative minimum)
- [ ] Research file created in docs/research/
- [ ] Citation coverage > 95%
- [ ] Average source reputation >= 0.80
**Distillation (if --skill-for specified):**
- [ ] Skill file created in ~/.claude/nWave/skills/{agent-name}/
- [ ] 100% essential concepts preserved
- [ ] Self-contained with no external references
- [ ] Token budget respected (<5000 tokens per skill)
Next Wave
**Handoff To**: Invoking workflow **Deliverables**: Research document + optional skill file
Examples
Example 1: Standalone research
/nw-research "event sourcing patterns" --research_depth=detailed
Nova researches event sourcing from trusted sources, cross-references 3+ sources per claim, produces comprehensive research document.
Example 2: Research with agent skill
/nw-research "mutation testing methodologies" --skill-for=software-crafter
Nova researches mutation testing, distills into practitioner-focused skill file at ~/.claude/nWave/skills/software-crafter/.
Expected Outputs
docs/research/{category}/{topic}-comprehensive-research.md
~/.claude/nWave/skills/{agent}/{topic}-methodology.md (if --skill-for)Default Trusted Sources
The following YAML is the default content for `.nwave/trusted-source-domains.yaml`. It is seeded automatically when the file does not exist.
# Trusted Source Domains for Evidence-Driven Research
# Used by knowledge-researcher agent to validate source credibility
# High-reputation academic and research sources
academic:
description: "Peer-reviewed academic and research institutions"
domains:
- "*.edu"
- "*.ac.uk"
- "scholar.google.com"
- "arxiv.org"
- "pubmed.ncbi.nlm.nih.gov"
- "researchgate.net"
- "ieee.org"
- "acm.org"
- "springer.com"
- "sciencedirect.com"
- "jstor.org"
- "nature.com"
- "science.org"
reputation: high
verification_requirements:
- peer_review_preferred
- citation_tracking
- author_credentials
# Official standards bodies and government sources
official:
description: "Government, standards organizations, and official documentation"
domains:
- "*.gov"
- "*.gov.uk"
- "w3.org"
- "ietf.org"
- "iso.org"
- "nist.gov"
- "docs.microsoft.com"
- "docs.oracle.com"
- "docs.python.org"
- "docs.oracle.com/javase"
- "kubernetes.io/docs"
- "docker.com/docs"
reputation: high
verification_requirements:
- official_publication
- version_tracking
- standards_compliance
# Industry leaders and recognized experts
industry_leaders:
description: "Established technology companies and recognized industry experts"
domains:
- "github.com"
- "stackoverflow.com"
- "martinfowler.com"
- "refactoring.guru"
- "enterpriseintegrationpatterns.com"
- "microservices.io"
- "12factor.net"
- "reactivemanifesto.org"
- "agilemanifesto.org"
- "thoughtworks.com/insights"
- "infoq.com"
reputatiRead more
description: "Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing." argument-hint: '[topic] - Optional: --research_depth=[overview|detailed|comprehensive|deep-dive] --skill-for=[agent-name]'
NW-RESEARCH: Evidence-Driven Knowledge Research
**Wave**: CROSS_WAVE **Agent**: Nova (nw-researcher) **Command**: `*research`
Overview
Systematic evidence-based research with source verification. Cross-wave support providing research-backed insights for any nWave phase using trusted academic|official|industry sources.
Optional `--skill-for={agent-name}` distills research into a practitioner-focused skill file for a specific agent.
Orchestration: Trusted Source Config
At orchestration time, before invoking the researcher subagent:
1. **Read** `.nwave/trusted-source-domains.yaml` from the project root 2. **If file missing**, seed it from the defaults in the `## Default Trusted Sources` section below, then notify the user: "Seeded `.nwave/trusted-source-domains.yaml` with defaults (7 categories, 42 trusted domains, 5 excluded). Edit the YAML directly to customize." 3. **Embed** the YAML content inline in the researcher subagent Task prompt so the agent receives trusted source config via prompt context
Agent Invocation
@nw-researcher
Execute \*research on {topic} [--skill-for={agent-name}].
**Configuration:**
- research_depth: detailed # overview/detailed/comprehensive/deep-dive
- source_preferences: ["academic", "official", "technical_docs"]
- output_directory: docs/research/
- skill_for: {agent-name} # Optional: distilled skill for specified agent
- skill_output_directory: ~/.claude/nWave/skills/{agent-name}/
Output Management
The researcher MUST create the output file in the FIRST 5 turns with a document skeleton (title, sections, placeholders). All subsequent findings are written DIRECTLY to this file as they are gathered -- never held only in context.
If the agent is interrupted or runs out of turns, the output file contains all work done so far. This is the researcher's equivalent of the crafter's "commit early, commit often."
Progressive write checkpoints:
- Turn ~5: Output file exists with skeleton
- Turn ~10: First findings written
- Turn ~25: All gathered findings written so far
- Turn ~35: Stop gathering, begin synthesizing
- Turn ~45+: Polish only
Progress Tracking
The invoked agent MUST create a task list from its workflow phases at the start of execution using TaskCreate. Each phase becomes a task with the gate condition as completion criterion. Mark tasks in_progress when starting each phase and completed when the gate passes. This gives the user real-time visibility into progress.
Success Criteria
**Research:**
- [ ] All sources from trusted source domains from prompt context
- [ ] Cross-reference performed (3+ sources per major claim ideal, 2 acceptable, 1 authoritative minimum)
- [ ] Research file created in docs/research/
- [ ] Citation coverage > 95%
- [ ] Average source reputation >= 0.80
**Distillation (if --skill-for specified):**
- [ ] Skill file created in ~/.claude/nWave/skills/{agent-name}/
- [ ] 100% essential concepts preserved
- [ ] Self-contained with no external references
- [ ] Token budget respected (<5000 tokens per skill)
Next Wave
**Handoff To**: Invoking workflow **Deliverables**: Research document + optional skill file
Examples
Example 1: Standalone research
/nw-research "event sourcing patterns" --research_depth=detailed
Nova researches event sourcing from trusted sources, cross-references 3+ sources per claim, produces comprehensive research document.
Example 2: Research with agent skill
/nw-research "mutation testing methodologies" --skill-for=software-crafter
Nova researches mutation testing, distills into practitioner-focused skill file at ~/.claude/nWave/skills/software-crafter/.
Expected Outputs
docs/research/{category}/{topic}-comprehensive-research.md
~/.claude/nWave/skills/{agent}/{topic}-methodology.md (if --skill-for)Default Trusted Sources
The following YAML is the default content for `.nwave/trusted-source-domains.yaml`. It is seeded automatically when the file does not exist.
# Trusted Source Domains for Evidence-Driven Research
# Used by knowledge-researcher agent to validate source credibility
# High-reputation academic and research sources
academic:
description: "Peer-reviewed academic and research institutions"
domains:
- "*.edu"
- "*.ac.uk"
- "scholar.google.com"
- "arxiv.org"
- "pubmed.ncbi.nlm.nih.gov"
- "researchgate.net"
- "ieee.org"
- "acm.org"
- "springer.com"
- "sciencedirect.com"
- "jstor.org"
- "nature.com"
- "science.org"
reputation: high
verification_requirements:
- peer_review_preferred
- citation_tracking
- author_credentials
# Official standards bodies and government sources
official:
description: "Government, standards organizations, and official documentation"
domains:
- "*.gov"
- "*.gov.uk"
- "w3.org"
- "ietf.org"
- "iso.org"
- "nist.gov"
- "docs.microsoft.com"
- "docs.oracle.com"
- "docs.python.org"
- "docs.oracle.com/javase"
- "kubernetes.io/docs"
- "docker.com/docs"
reputation: high
verification_requirements:
- official_publication
- version_tracking
- standards_compliance
# Industry leaders and recognized experts
industry_leaders:
description: "Established technology companies and recognized industry experts"
domains:
- "github.com"
- "stackoverflow.com"
- "martinfowler.com"
- "refactoring.guru"
- "enterpriseintegrationpatterns.com"
- "microservices.io"
- "12factor.net"
- "reactivemanifesto.org"
- "agilemanifesto.org"
- "thoughtworks.com/insights"
- "infoq.com"
reputatiAI agents that guide you from idea to working code, with human judgment at every gate. nWave runs inside Claude Code. It breaks feature delivery into seven waves (discover, diverge, discuss, design, devops, distill, deliver).
Repo: nWave-ai/nWave
Other commands on nwave.
- /buddy
nWave concierge โ ask any question about methodology, project state, commands, migration, or troubleshooting. Read-only, contextual answers.
Open command - /bugfix
Bug fix workflow: root cause analysis โ user review โ regression test + fix via TDD
Open command - /continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
Open command - /deliver
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.
Open command - /design
Designs system architecture with C4 diagrams and technology selection. Use when defining component boundaries, choosing tech stacks, or creating architecture documents.
Open command - /devops
Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature.
Open command

