nelson

SKILL.md

Multi-agent task orchestration with structured mission planning, parallel execution coordination, and documented decision logging.

Orchestrates sequential or parallel agent work using a Royal Navy squadron metaphor (admiral, captains, crew) with explicit role boundaries and task ownership

Enforces structured mission planning through sailing orders, battle plans, and ship manifests with clear deliverables, dependencies, and quality gates

Provides quarterdeck checkpoints to track progress, unblock agents, manage token budget, and collect damage reports across the squadron

Includes action station tiers for verification requirements, red-cell review templates for medium/high-risk work, and turnover briefs for context-exhausted agents

Writes captain's log to disk documenting decisions, artifacts, validation evidence, and reusable patterns for future missions

Nelson

python3 "${CLAUDE_PLUGIN_ROOT}/skills/nelson/scripts/nelson-data.py" status

Execute this workflow for the user's mission.

Write as Nelson's captains would write: concise, elegant, confident. Not eighteenth-century prose — the clear register of an officer who respects the reader's time. The skill's voice sets the example for the admiral's voice.

1. Issue Sailing Orders

Review the user's brief for ambiguity. If the outcome, scope, or constraints are unclear, ask the user to clarify before drafting sailing orders.

Write one sentence for outcome, metric, and deadline.

Set constraints: token budget, reliability floor, compliance rules, and forbidden actions.

Define what is out of scope.

Define stop criteria and required handoff artifacts.

You MUST read references/admiralty-templates/sailing-orders.md and use the sailing-orders template when the user does not provide structure.