nelson
NewRoyal Navy agent coordination framework â sailing orders, battle plans, action stations, and a captain's log
Summary
Nelson is a Royal Navy-inspired agent coordination framework that helps developers orchestrate multi-agent workflows using sailing orders, battle plans, and action stations.
- It provides a structured command hierarchy for managing teams of AI agents, tracking their status in a captain's log, and executing coordinated tasks with clear roles and dependencies.
Install & Usage
mkdir -p .claude/agentsAdd the configuration to .claude/agents/nelson.md
@nelsonUse Cases
Usage Examples
/nelson sailing-orders "Deploy the latest release to staging, run integration tests, and report results"
/nelson battle-plan "Plan the migration of the user service from monolith to microservices with agents for database, API, and testing"
/nelson action-stations "Monitor the payment gateway logs and escalate any 5xx errors to the on-call agent"
Security Audits
Frequently Asked Questions
What is nelson?
Nelson is a Royal Navy-inspired agent coordination framework that helps developers orchestrate multi-agent workflows using sailing orders, battle plans, and action stations. It provides a structured command hierarchy for managing teams of AI agents, tracking their status in a captain's log, and executing coordinated tasks with clear roles and dependencies.
How to install nelson?
To install nelson: create the agents directory (mkdir -p .claude/agents), then add the config to .claude/agents/nelson.md. Finally, @nelson in Claude Code.
What is nelson best for?
nelson is a agent categorized under General. It is designed for: agent, agents, coordination, teams, workflow. Created by Harry Munro.
What can I use nelson for?
nelson is useful for: Coordinate a team of agents to build a full-stack application, with each agent handling frontend, backend, and database tasks in parallel.; Run a battle plan simulation where agents execute sequential steps like code review, testing, and deployment with rollback safeguards.; Assign action stations to agents for monitoring production logs and automatically triggering fixes when anomalies are detected.; Use the captain's log to track the progress of a multi-agent code migration project across multiple repositories.; Orchestrate a swarm of agents to perform competitive analysis by scraping competitor sites, summarizing findings, and generating a report.; Define sailing orders for a daily standup agent that collects status updates from other agents and compiles a summary for the team..