battle-plan

Name: battle-plan
Availability: InStock
Author: Elliot

Orchestrate a phased planning ritual for development work.

60|2|Updated Jan 21, 2026

Search Tags:#workflow #planning #estimation #confirmation #risk-analysis #pre-mortem #rubber-duck

Ready to run

npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill battle-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: battle-plan
Source: https://github.com/ElliotJLT/Claude-Skill-Potions/tree/main/skills/battle-plan
Command: npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill battle-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable planning ritual to align teams and avoid scope creep before significant development work.

Core Features & Use Cases

Orchestrates a multi-phase planning flow (Scope, Recon, Risks, Estimate, The Plan, Confirmation) by leveraging composable skills when available.
Ensures explicit definitions of done, boundaries, and risk mitigation before any coding begins.
Use cases include new features, major refactors, external integrations, and migrations.

Quick Start

Invoke the battle-plan skill to generate a formal plan for a feature, then proceed with execution only after approval. For example: "Plan the new payment integration" then review and confirm the plan before coding.

Frequently Asked Questions about battle-plan

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

FAQPage Schema

How do I plan a major development project before coding begins?▼

Planning before coding establishes scope, identifies risks, estimates effort, and gates execution. Battle-plan orchestrates a phased ritual—Scope, Recon, Risks, Estimate, The Plan, Confirmation—to align teams, prevent scope creep, and ensure explicit definitions of done and risk mitigation across new features, refactors, integrations, and migrations.

What's the best way to estimate effort and identify risks upfront?▼

Structured risk analysis and effort estimation happen in dedicated phases within a planning ritual. Battle-plan enforces a sequence that surfaces hidden assumptions, validates boundaries, quantifies effort, and documents mitigation strategies before work begins, reducing rework and surprises.

How do I confirm a development plan is ready for execution?▼

A confirmation phase gates execution and ensures stakeholder alignment. Battle-plan requires explicit approval of scope, estimates, and risk mitigations before coding starts, catching misalignment early and reducing derailed projects.

Can I integrate planning with rubber-duck debugging and pre-mortem analysis?▼

Yes. Battle-plan composes adjacent skills like rubber-duck, pre-mortem, eta, and you-sure when installed, allowing you to layer specialized techniques—rubber-duck for assumption validation, pre-mortem for failure analysis—into your planning workflow.

When should I use a structured planning ritual for a development task?▼

Use structured planning for new features, major refactors, external integrations, and migrations—tasks requiring cross-functional alignment, explicit boundaries, and risk assessment. Smaller, routine work may not justify the full ritual.