Orchestrate a phased planning ritual for development work.
npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill battle-plan
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
This skill provides a structured, repeatable planning ritual to align teams and avoid scope creep before significant development work.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
BellaBeTransform Canvas strategy into structured product requirements and user stories.
hemoryAnalyze goal completion, task progress, and meeting outcomes into a structured quarterly review document.
FrogAiGuide users through structured, purpose-labeled questions to surface hidden assumptions.
nicepkgGuide Agile product management with Scrum, Kanban, and SAFe practices.
