Add Royal Marines — sub-agents for captains

[harrymunro]

Summary

• Introduces Royal Marines — sub-agents a captain deploys for focused, independent objectives (recon, targeted fixes, quick infra tasks) without crewing a full role or requesting a new ship
• Adds three marine specialisations: Recce Marine (read-only reconnaissance), Assault Marine (targeted changes), and Sapper (engineering support)
• Adds the Battalion Ashore anti-pattern to prevent misuse of marines for crew work or sustained tasks
• Adds a lightweight Marine Deployment Brief template (~200 tokens, lighter than crew briefings)
• Integrates marine references across SKILL.md, crew-roles, ship-manifest, action-stations, and both index files

Files created

File	Purpose
references/royal-marines.md	Main reference: specialisations, deployment rules, station interaction, recovery
references/standing-orders/battalion-ashore.md	Anti-pattern: deploying marines for crew work
references/admiralty-templates/marine-deployment-brief.md	Lightweight deployment briefing template

Files modified

File	Change
SKILL.md	Steps 2-5: marine references in squadron, battle plan, quarterdeck, action stations
references/crew-roles.md	New section clarifying crew vs. marine distinction
references/admiralty-templates/ship-manifest.md	Optional Marine capacity field
references/admiralty-templates.md	Index entry for marine deployment brief
references/standing-orders.md	Index entry for Battalion Ashore
references/action-stations.md	Marine deployment station-tier rules

Test plan

• Install updated skill into a test project
• Invoke /nelson on a mission that produces a marine deployment opportunity
• Verify ship manifest includes marine capacity field
• Verify captain identifies marine vs. crew work correctly
• Verify marine deployment brief template is used
• Verify station-tier rules are respected (Station 0-1 free, Station 2 requires admiral)
• Verify Battalion Ashore is flagged if marines are misused

---

In memory of Harrison Owens, Royal Marine, 1994–2024.

[harrymunro]

Marine deployment tested and fixed

Problem: The crew briefing told captains about marines but didn't give them enough detail to actually deploy one. In testing, a captain tried to launch a nested claude CLI process via Bash instead of using the built-in Task tool.

Fix (ce0e82c): Made the crew briefing's marine instructions explicit:

• "NOT via bash/CLI — use the built-in Task tool"
• Exact subagent_type values inline (Explore for Recce, general-purpose for Assault/Sapper)
• Inlined the deployment brief template so captains don't need to load a separate reference file

Verification: Re-ran the test — HMS Daring successfully deployed a Recce Marine to scout the damage-control/ directory, got the intel back, and used it for cross-reference analysis. No errors.

[harrymunro]

Post-merge verification — Royal Marines integration

Merged main into royal-marines and re-verified that all marine references survive the skill relocation (.claude/skills/nelson/ → skills/nelson/).

Checklist

#	Check	Result
1	references/royal-marines.md exists and is complete (decision tree, specialisations, deployment rules, station-tier interaction, recovery)	✅
2	admiralty-templates/marine-deployment-brief.md template exists with all fields	✅
3	standing-orders/battalion-ashore.md anti-pattern doc exists (symptoms + remedy)	✅
4	SKILL.md references marines in Step 2 (Form the Squadron) and Step 5 (Action Stations) with correct paths	✅
5	Cross-references intact: admiralty-templates.md index lists marine brief, standing-orders.md lists battalion-ashore, crew-roles.md mentions marines, crew-briefing.md includes deployment instructions	✅
6	No stale references to old .claude/skills/nelson/ path in skill files	✅
7	scripts/check-references.sh runs clean — all cross-references valid, no orphans	✅
8	Old .claude/skills/nelson/ directory fully removed, no orphaned files	✅

All 8 checks pass. Marines deploy correctly after the merge.