📋 Inventory-driven
Detects installed packages, versions, and enabled features — template routing, Quartermaster, WooCommerce — and briefs accordingly.
$ wp package install pressgang-wp/bosun$ wp bosun install ✔ Inventory: pressgang 2.1 · quartermaster 1.3✔ Template routing detected — guidance aboard✔ Composed CLAUDE.md + AGENTS.md✔ Skills installed → .claude/skills/✔ MCP server registered → .mcp.json All hands briefed.The problem
Convention is invisible to an unbriefed agent
PressGang's best features leave barely a trace in a child theme's code — controllers route by convention, config merges silently, context getters wire themselves. Great for developers who know the ship; invisible to AI agents who don't.
An unbriefed agent writes working code that misses everything the framework gives you: hand-rolled query arrays, stub template files, hooks in functions.php. Bosun closes that gap at the source.
# harbour-cafe — agent guidelines ## Template routing is ONDo not create archive-*.php stubs.Controllers resolve by convention. ## Queries use Quartermaster 1.3Prefer fluent methods over raw args. ## Post types live in config/Never register via add_action('init').Composed from the ship's manifest
Not a static template pasted into every repo — Bosun inspects each theme and writes guidance for what's actually there.
🧠 Every agent format
Writes CLAUDE.md and AGENTS.md, plus agent skills — one briefing, every AI coding tool aboard.
🔄 Re-run anytime
Add a package, enable a feature, re-run wp bosun install — the briefing keeps pace with the ship.
🔌 Live tools, not just docs
Where Capstan can serve MCP, Bosun wires its introspection — routing, config, health, version-aware docs search — straight into your editor's .mcp.json, so agents observe the live theme, not just read about it.
Built for the PressGang fleet
Bosun completes the loop: Capstan launches the project, PressGang structures it, Quartermaster queries it — and Bosun makes sure your AI tools know all of it.