/forge
Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification.
> /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
/forge
Context preview
What this command does when you run it.
Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification.
Command definition
forge.mddescription: "Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification."
argument-hint: '[agent-name] - Optional: --type=[specialist|reviewer|orchestrator] --pattern=[react|reflection|router]'
NW-FORGE: Create Agent (V2)
**Wave**: CROSS_WAVE **Agent**: Zeus (nw-agent-builder)
Overview
Create a new agent using research-validated v2 approach: focused core (200-400 lines) with Skills for domain knowledge. 5-phase workflow: ANALYZE > DESIGN > CREATE > VALIDATE > REFINE.
Agent Invocation
@nw-agent-builder
Execute \*forge to create {agent-name} agent.
**Configuration:**
- agent_type: specialist | reviewer | orchestrator
- design_pattern: react | reflection | router | planning | sequential | parallel | hierarchical
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
- [ ] Agent definition under 400 lines (`wc -l`)
- [ ] Official YAML frontmatter format (name, description, tools, maxTurns)
- [ ] 11-point validation checklist passes
- [ ] Only divergent behaviors specified (no Claude defaults)
- [ ] 3-5 canonical examples included
- [ ] Domain knowledge extracted to Skills if >50 lines
- [ ] No aggressive language (no CRITICAL/MANDATORY/ABSOLUTE)
- [ ] Safety via platform features (frontmatter/hooks), not prose
Next Wave
**Handoff To**: Agent installation and deployment **Deliverables**: Agent specification file + Skill files (if any)
Expected Outputs
~/.claude/agents/nw/nw-{agent-name}.md
~/.claude/skills/nw/{agent-name}/*.md (if Skills needed)Read more
description: "Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification." argument-hint: '[agent-name] - Optional: --type=[specialist|reviewer|orchestrator] --pattern=[react|reflection|router]'
NW-FORGE: Create Agent (V2)
**Wave**: CROSS_WAVE **Agent**: Zeus (nw-agent-builder)
Overview
Create a new agent using research-validated v2 approach: focused core (200-400 lines) with Skills for domain knowledge. 5-phase workflow: ANALYZE > DESIGN > CREATE > VALIDATE > REFINE.
Agent Invocation
@nw-agent-builder
Execute \*forge to create {agent-name} agent.
**Configuration:**
- agent_type: specialist | reviewer | orchestrator
- design_pattern: react | reflection | router | planning | sequential | parallel | hierarchical
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
- [ ] Agent definition under 400 lines (`wc -l`)
- [ ] Official YAML frontmatter format (name, description, tools, maxTurns)
- [ ] 11-point validation checklist passes
- [ ] Only divergent behaviors specified (no Claude defaults)
- [ ] 3-5 canonical examples included
- [ ] Domain knowledge extracted to Skills if >50 lines
- [ ] No aggressive language (no CRITICAL/MANDATORY/ABSOLUTE)
- [ ] Safety via platform features (frontmatter/hooks), not prose
Next Wave
**Handoff To**: Agent installation and deployment **Deliverables**: Agent specification file + Skill files (if any)
Expected Outputs
~/.claude/agents/nw/nw-{agent-name}.md
~/.claude/skills/nw/{agent-name}/*.md (if Skills needed)AI 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

