Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Organisation for Claude Code inspired by time-tested Royal Navy operating procedures.
| Date | Stars |
|---|---|
| 2026-07-31 | 408 |
| 2026-08-04 | 409 |
| 2026-08-06 | 409 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# Nelson [](https://github.com/harrymunro/nelson/releases) [](LICENSE) [](https://docs.anthropic.com/en/docs/claude-code) [](https://github.com/harrymunro/nelson/stargazers) **If you believe that what works well for people works well for agents, there's few finer examples of organisational tradition than the Royal Navy to base the rules on. This framework does just that, for Claude Code.** <!-- markdownlint-disable-next-line MD036 --> *4 risk tiers · 11 damage control procedures · 11 mission templates · 7 crew roles · 16 standing orders* <p align="center"> <img src="docs/images/1024px-Young_Nelson-min.jpg" alt="Captain Horatio Nelson" width="500"> <br> <em>Captain Horatio Nelson — John Francis Rigaud, 1781. Image: Wikimedia Commons</em> </p> ## Contents - [Quick Start](#quick-start) - [What it does](#what-it-does) - [Why Nelson?](#why-nelson) - [How it works](#how-it-works) - [Prerequisites](#prerequisites) - [Installation](#installation) - [Usage](#usage) - [Customisation](#customisation) - [Plugin file structure](#plugin-file-structure) - [Mission artifacts](#mission-artifacts) - [Compatibility notes](#compatibility-notes) - [Star History](#star-history) - [Disclaimer](#disclaimer) - [License](#license) ## Quick Start Install the plugin: ``` /plugin marketplace add harrymunro/nelson /plugin install nelson@nelson-marketplace ``` Describe your mission — Nelson loads automatically, no slash command needed: ``` Use Nelson to migrate the payment module from Stripe v2 to v3 ``` Nelson will draft sailing orders, present a battle plan for your approval, form a squadron of captains to execute in parallel, run quarterdeck checkpoints, and produce a captain's log when the mission stands down. See [Prerequisites](#prerequisites) for the full agent-team experience with split panes. ## What it does https://github.com/user-attachments/assets/2468679d-39f5-4efb-9d93-43d43eee8907 Nelson gives Claude an eight-step operational framework for tackling complex missions: 1. **Sailing Orders** — Define the outcome, success metric, constraints, and stop criteria 2. **The Estimate** — Conduct the 7 Question Maritime Tactical Estimate: reconnaissance, intent, effects, terrain, forces, coordination, and control 3. **Battle Plan** — Turn approved effects into task assignments with owners, dependencies, and file ownership 4. **Form the Squadron** — Choose an execution mode (single-session, subagents, agent team, workflow, or hybrid workflow) and size the team 5. **Get Permission to Sail** — Present the plan for user approval before committing resources 6. **Quarterdeck Rhythm** — Run checkpoints to track progress, identify blockers, monitor hull integrity, and manage budget 7. **Action Stations** — Classify tasks by risk tier and enforce verification before marking complete 8. **Stand Down** — Produce a captain's log with decisions, artifacts, validation evidence, and follow-ups ## Why Nelson? Most agent orchestration tools focus on starting missions. Nelson focuses on completing them safely. Nelson gives your missions a shared vocabulary: "action stations" instead of "risk tier escalation", "hull integrity" instead of "context window consumption", "man overboard" instead of "stuck agent replacement". The names stick. So do the habits. - **Risk-gated execution** — Four station tiers (Patrol through Trafalgar) classify every task before it runs. High-risk work requires human confirmation; low-risk work flows without ceremony. - **Damage control built in** — Eleven named procedures for stuck agents, context exhaustion, faulty output, budget overruns, automated alarms, and mission abort. These are protocols, not improvisation. - **A decision log by default** — Captain
Excerpt of 34,497 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:9d812c41ad8af8e7, topic:ai-agents