name	ooda
description	Apply Boyd's OODA loop — observe, orient, decide, act — emphasising fast iteration over deep deliberation. Best for fast-moving or adversarial decisions. Produces a 0-100 score.

OODA Loop

Single-framework analysis. Use when the user wants this lens specifically, or when called as a building block by /decision:analyze.

A decision file path (markdown). If the user describes a decision verbally instead, run /decision:new-decision first.

Locate the framework guide at the plugin install dir's frameworks/ooda.md. Read it fully.
Read the decision file fully.
Apply the framework exactly as the guide specifies. Don't invent additional structure. Don't merge in other frameworks — that's the orchestrator's job.
Output destination:
- If the user invoked this standalone, write the analysis inline as the response (and offer to save it to a path).
- If invoked as a subagent by /decision:analyze, write to the fragment path the orchestrator provides (fragments/ooda.md).
End with the score line ## Score: <0-100> per the guide's scoring rubric.

Stay inside the framework. If you notice that a different framework would have surfaced something this one missed, note it briefly at the end (## Cross-framework note) but don't switch lenses.

name	ooda
description	Apply Boyd's OODA loop — observe, orient, decide, act — emphasising fast iteration over deep deliberation. Best for fast-moving or adversarial decisions. Produces a 0-100 score.

Single-framework analysis. Use when the user wants this lens specifically, or when called as a building block by /decision:analyze.

A decision file path (markdown). If the user describes a decision verbally instead, run /decision:new-decision first.

Locate the framework guide at the plugin install dir's frameworks/ooda.md. Read it fully.
Read the decision file fully.
Apply the framework exactly as the guide specifies. Don't invent additional structure. Don't merge in other frameworks — that's the orchestrator's job.
Output destination:
- If the user invoked this standalone, write the analysis inline as the response (and offer to save it to a path).
- If invoked as a subagent by /decision:analyze, write to the fragment path the orchestrator provides (fragments/ooda.md).
End with the score line ## Score: <0-100> per the guide's scoring rubric.

Stay inside the framework. If you notice that a different framework would have surfaced something this one missed, note it briefly at the end (## Cross-framework note) but don't switch lenses.

ooda