Battle Plan
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
Install
npx skills add ElliotJLT/Claude-Skill-Potions --skill battle-plangit clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/battle-plan ~/.claude/skills/battle-planPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Battle Plan <purpose> Claude Code's built-in plan mode is just "read-only mode + write a markdown file." It doesn't assess risks, estimate time, define done, or check scope. This skill orchestrates a complete planning ritual using composable skills before any significant work begins. </purpose> ## When To Activate Trigger before: - New feature implementation - Refactors touching multiple files - External service integrations - Database migrations - "Significant" or "important" tasks (user's words) - Anything estimated >15 minutes Do NOT trigger for: - Typo fixes - Single-line changes - Questions/exploration - Tasks user explicitly says are trivial ## Instructions ### Phase 1: Scope (uses [rubber-duck](../rubber-duck/SKILL.md) patterns) Before anything, clarify what we're actually building: ``` Scope Check What are we building? -> [Clear description of the goal] What's the definition of done? -> [Specific, verifiable completion criteria] What's explicitly OUT of scope? -> [Things we're NOT doing, even if related] Any ambiguity I should clarify before planning? ``` If scope is vague, ask clarifying questions. Do not proceed with vague scope. ### Phase 2: Recon Map the terrain before planning the attack: ``` Recon Files likely affected: - [file1.py] - [why] - [file2.py] - [why] Existing patterns to follow: - [Pattern observed in codebase] Dependencies/callers to check: - [What depends on code we're changing] Tests that exist: - [Relevant test files] ```
Details
- Skill name
battle-plan- Repository
- ElliotJLT/Claude-Skill-Potions
- Path
skills/battle-plan/SKILL.md- License
- MIT
- Repo updated
- 12 February 2026
FAQ
What does the Battle Plan skill do?
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
How do I install the Battle Plan skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill battle-plan. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Battle Plan popular?
It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.
Related skills
Agent Audit
62ElliotJLT/Claude-Skill-Potions
When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.
Breadcrumbs
62ElliotJLT/Claude-Skill-Potions
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
Careful Delete
62ElliotJLT/Claude-Skill-Potions
Before any destructive or irreversible operation (rm -rf, DROP TABLE, DELETE, force push, branch deletion, truncate), orchestrate a safety cycle: assess blast radius → confirm explicitly → document what happened. Chains pre-mortem and you-sure with built-in documentation. No dangerous operation executes without ceremony.
Brainstorming Ideas Into Designs
43obra/clank
Interactive idea refinement using Socratic method to develop fully-formed designs
Advanced Code Quality
38sam-dumont/claude-skills
Use when going beyond basic linting to enforce advanced Python code quality gates. Triggers on: cognitive complexity, code duplication detection, architectural enforcement, import boundaries, dependency hygiene, test quality beyond coverage, mutation testing, docstring coverage, type coverage, AI-generated code detection, AI slop detection, complexipy, jscpd, import-linter, deptry, diff-cover, mutmut, interrogate, sloppylint, refurb, pylint design checks, wily, radon maintainability, pytestarch, griffe, "bulletproof Python", "tighten quality gates", "advanced quality checks", "beyond ruff and
Code Quality
38sam-dumont/claude-skills
Automatically triggered when setting up Python code quality tooling, configuring linters, adding type checking, improving code standards, running code quality checks, setting up pre-commit hooks, or auditing Python code for quality issues. Applies when discussing: ruff setup, mypy configuration, code formatting, linting rules, cyclomatic complexity, dead code detection, file length limits, pre-commit hooks, Makefile targets for quality, uv-based workflows, pyproject.toml configuration, or "check my code quality". Also triggers on: "set up linting", "add type checking", "configure ruff", "forma
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.