admiralty

Drafts sailing orders and a battle plan from repository-grounded task descriptions.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/sandeepkv93/admiralty --skill admiralty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: admiralty
Source: https://github.com/sandeepkv93/admiralty/tree/main
Command: npx skills add https://github.com/sandeepkv93/admiralty --skill admiralty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Draft structured sailing orders for a Nelson mission from a task description.

Core Features & Use Cases

  • Repository-grounded planning: ground the plan in the observed repository state.
  • Phase-driven workflow: Reconnoitre, Assess, Draft Orders, Signal.
  • Output artifacts: Sailing Orders and Battle Plan ready for execution frameworks.

Quick Start

Provide a task description and let Admiralty draft orders and a battle plan aligned to the current codebase.

Frequently Asked Questions about admiralty

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a task brief into a structured battle plan grounded in my codebase?

To convert a task brief into a structured battle plan, provide the task description to generate repository-grounded sailing orders. This produces ownership, dependency, risk, validation, and rollback notes by analyzing the current codebase state.

What is repository-grounded planning for software projects?

Repository-grounded planning grounds project execution in the observed codebase state. It uses a four-phase workflow—Reconnoitre, Assess, Draft Orders, Signal—to generate structured sailing orders and a battle plan with risk assessments.

Can I use Codex or Claude integrations to execute a codebase battle plan?

Yes, you can use Codex or Claude integrations to execute the generated battle plan. The Skill outputs sailing orders and battle plans specifically formatted to feed into these execution frameworks.

How does the four-phase workflow produce sailing orders and risk assessments?

The four-phase workflow—Reconnoitre, Assess, Draft Orders, Signal—produces sailing orders by analyzing the repository, assessing risks, drafting execution plans, and signaling readiness. It outputs ownership, dependencies, and rollback notes.

Do I need to provide a task description to generate sailing orders for a software project?

Yes, you need to provide a task description to generate sailing orders. The Skill analyzes this brief against the current codebase state to draft a structured battle plan with validation and rollback notes.

What's the best way to assess codebase risks before starting a development mission?

The best way to assess codebase risks before a development mission is using a phase-driven workflow that evaluates repository state and drafts structured sailing orders. This yields a battle plan with ownership, dependencies, and rollback notes.