Battle Analysis — The Staff Ride Method
This is an action skill that produces structured analyses of specific historical battles and campaigns. It adapts the US Army's Staff Ride methodology — designed to teach officers by walking battlefields — into an analytical framework that works without being on-site. The goal is not to narrate what happened but to understand why it happened and what it teaches.
Every battle analysis connects upward to strategic context (via strategy-and-grand-strategy) and outward to the technological/operational context (via warfare-through-the-ages).
When This Applies
- User names a specific battle ("Tell me about Cannae / Stalingrad / Midway")
- User asks "what happened at [battle]" in an analytical rather than narrative mode
- User wants to understand why a battle was won or lost
- User wants to extract leadership or strategic lessons from a military engagement
The Seven-Step Analysis
Step 1 — Strategic Context
Why was this battle fought? What were the political and military objectives?
- What war is this part of? What are the belligerents' war aims?
- What is the campaign context? Where does this battle fit in the larger operational sequence?
- What were each side's strategic objectives for this engagement?
Step 2 — Force Composition
Who fought, and with what?
- Approximate numbers for each side (infantry, cavalry, armor, air, naval)
- Quality factors: training, experience, morale, equipment condition
- Command structure: who was in charge? What was the command relationship?
- Logistics: supply situation, lines of communication, reinforcement availability
Step 3 — Terrain and Conditions
Where and when?
- Key terrain features and their tactical significance
- Weather and its impact on operations
- Infrastructure: roads, bridges, communications, fortifications
- How did terrain advantage/disadvantage each side?
Step 4 — Plans and Intentions
What did each side intend to do?
- Each commander's plan and its underlying assumptions
- What intelligence did each side have about the other?
- Where were the plans realistic? Where were they based on faulty assumptions?
Step 5 — Execution
What actually happened?
- The key phases of the battle in chronological order
- Where did plans survive contact with reality? Where did they break down?
- What decisions were made under pressure? What were the alternatives?
- Clausewitz's friction: what went wrong that no one planned for?
Step 6 — The Decisive Moment
What determined the outcome?
- Identify the turning point — the moment after which the outcome became likely
- Was it a command decision, a technological factor, a logistical reality, or chance?
- Could the losing side have changed the outcome? At what point did the battle become irreversible?
Step 7 — Lessons and Legacy
What does this battle teach?
- What principles of strategy/tactics does it illustrate or complicate?
- How did this battle influence subsequent military thinking?
- What would a different decision at the decisive moment have changed?
- Connect to broader patterns: Does this illustrate offense-defense balance? Overstretch? Intelligence failure?
Output Template
BATTLE: [Name, Date]
WAR/CAMPAIGN: [Context]
BELLIGERENTS: [Side A vs. Side B]
STRATEGIC CONTEXT:
[Why this battle was fought; political/military objectives]
FORCES:
[Side A]: [Numbers, composition, quality, commander]
[Side B]: [Numbers, composition, quality, commander]
TERRAIN: [Key features and their significance]
PLANS:
[Side A]: [What they intended]
[Side B]: [What they intended]
EXECUTION:
[Key phases chronologically; where plans broke down]
DECISIVE MOMENT:
[The turning point and why it determined the outcome]
OUTCOME: [Winner, casualties, territorial result]
LESSONS:
1. [Strategic/tactical principle illustrated]
2. [Leadership lesson]
3. [Connection to broader historical pattern]
LEGACY: [How this battle influenced subsequent history/thinking]
Anti-Patterns
- "Great man" fallacy: Don't attribute outcomes solely to commander genius/failure — structural factors (logistics, terrain, technology, numbers) usually matter more
- Hindsight bias: Don't judge decisions by outcomes; judge them by what the commander reasonably knew at the time
- Narrative smoothing: Real battles are chaotic; resist the temptation to impose clean storylines on messy events
- Ignoring the losers: Analyze both sides; the losing side's decisions are often more instructive than the winner's
1---2name: battle-analysis3description: Produce structured analyses of historical battles and campaigns using the US Army Staff Ride methodology adapted for analytical learning. Use when the user wants to understand a specific battle's strategic context, force composition, terrain, plan versus execution, the decisive moment, and what it teaches about warfare and leadership.4---56# Battle Analysis — The Staff Ride Method78This is an action skill that produces structured analyses of specific historical battles and campaigns. It adapts the US Army's Staff Ride methodology — designed to teach officers by walking battlefields — into an analytical framework that works without being on-site. The goal is not to narrate what happened but to understand *why* it happened and *what it teaches*.910Every battle analysis connects upward to strategic context (via `strategy-and-grand-strategy`) and outward to the technological/operational context (via `warfare-through-the-ages`).1112## When This Applies1314- User names a specific battle ("Tell me about Cannae / Stalingrad / Midway")15- User asks "what happened at [battle]" in an analytical rather than narrative mode16- User wants to understand why a battle was won or lost17- User wants to extract leadership or strategic lessons from a military engagement1819## The Seven-Step Analysis2021### Step 1 — Strategic Context2223*Why was this battle fought? What were the political and military objectives?*2425- What war is this part of? What are the belligerents' war aims?26- What is the campaign context? Where does this battle fit in the larger operational sequence?27- What were each side's strategic objectives for this engagement?2829### Step 2 — Force Composition3031*Who fought, and with what?*3233- Approximate numbers for each side (infantry, cavalry, armor, air, naval)34- Quality factors: training, experience, morale, equipment condition35- Command structure: who was in charge? What was the command relationship?36- Logistics: supply situation, lines of communication, reinforcement availability3738### Step 3 — Terrain and Conditions3940*Where and when?*4142- Key terrain features and their tactical significance43- Weather and its impact on operations44- Infrastructure: roads, bridges, communications, fortifications45- How did terrain advantage/disadvantage each side?4647### Step 4 — Plans and Intentions4849*What did each side intend to do?*5051- Each commander's plan and its underlying assumptions52- What intelligence did each side have about the other?53- Where were the plans realistic? Where were they based on faulty assumptions?5455### Step 5 — Execution5657*What actually happened?*5859- The key phases of the battle in chronological order60- Where did plans survive contact with reality? Where did they break down?61- What decisions were made under pressure? What were the alternatives?62- Clausewitz's friction: what went wrong that no one planned for?6364### Step 6 — The Decisive Moment6566*What determined the outcome?*6768- Identify the turning point — the moment after which the outcome became likely69- Was it a command decision, a technological factor, a logistical reality, or chance?70- Could the losing side have changed the outcome? At what point did the battle become irreversible?7172### Step 7 — Lessons and Legacy7374*What does this battle teach?*7576- What principles of strategy/tactics does it illustrate or complicate?77- How did this battle influence subsequent military thinking?78- What would a different decision at the decisive moment have changed?79- Connect to broader patterns: Does this illustrate offense-defense balance? Overstretch? Intelligence failure?8081## Output Template8283```84BATTLE: [Name, Date]85WAR/CAMPAIGN: [Context]86BELLIGERENTS: [Side A vs. Side B]8788STRATEGIC CONTEXT:89 [Why this battle was fought; political/military objectives]9091FORCES:92 [Side A]: [Numbers, composition, quality, commander]93 [Side B]: [Numbers, composition, quality, commander]9495TERRAIN: [Key features and their significance]9697PLANS:98 [Side A]: [What they intended]99 [Side B]: [What they intended]100101EXECUTION:102 [Key phases chronologically; where plans broke down]103104DECISIVE MOMENT:105 [The turning point and why it determined the outcome]106107OUTCOME: [Winner, casualties, territorial result]108109LESSONS:110 1. [Strategic/tactical principle illustrated]111 2. [Leadership lesson]112 3. [Connection to broader historical pattern]113114LEGACY: [How this battle influenced subsequent history/thinking]115```116117## Anti-Patterns118119- **"Great man" fallacy**: Don't attribute outcomes solely to commander genius/failure — structural factors (logistics, terrain, technology, numbers) usually matter more120- **Hindsight bias**: Don't judge decisions by outcomes; judge them by what the commander reasonably knew at the time121- **Narrative smoothing**: Real battles are chaotic; resist the temptation to impose clean storylines on messy events122- **Ignoring the losers**: Analyze both sides; the losing side's decisions are often more instructive than the winner's
npbuilds