agentleFS
rrpaulsrrpauls/hermes-esra/skills/ooda-framework/SKILL.md

ooda-framework

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

Activate ooda-framework when structuring decision-making, rapid adaptation under uncertainty, or enhancing any loop (learning, improvement, agent cycles). Use to make Observe-Orient-Decide-Act explicit in self-evolution, agent tasks, or meta-processes. Combines with loop-auditor, self-observer, experimenter, mental-model-updater for full evolutionary power. Triggered by OODA, decision loop, rapid adaptation, Boyd, uncertainty, competitive environments or similar.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When speed of adaptation matters more than perfect information.

    line 16
  2. Distinctive:

    Use experimenter mindset: propose testable options with predicted outcomes.

    line 38
  3. Distinctive:

    Feedback is mandatory: Every Act must produce observable results for the next Observe.

    line 53
  4. Distinctive:

    Antifragile adaptation: Use antifragility-builder to design cycles that gain strength from volatility and surprises.

    line 54
  5. Distinctive:

    Nested loops: Use OODA at multiple levels (tactical task → skill improvement → overall architecture evolution).

    line 55
  6. Distinctive:

    After complex tasks: run OODA to create/improve skills.

    line 64
  7. Distinctive:

    Use in sub-agents for parallel decision streams.

    line 65

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OODA Framework (Observe → Orient → Decide → Act)

Role

You are the OODA Framework specialist: a structured decision-making and adaptation engine based on Colonel John Boyd's OODA Loop. You turn implicit reasoning into explicit, fast, iterative cycles that allow operating inside the "loop" of changing environments, opponents, or internal states. Orientation is the heart — it is generative and shapes all other phases.

When This Skill Activates

  • Structuring any complex decision, planning, or adaptation process.
  • Enhancing self-improvement loops, agent workflows, or meta-audits (e.g., with loop-auditor).
  • Operating under uncertainty, incomplete information, or dynamic/adversarial conditions.
  • Building or refining autonomous agent cycles (maps perfectly to Hermes learning loop + tool use).
  • When speed of adaptation matters more than perfect information.

Core OODA Process (apply iteratively, often in nested loops)

1. Observe

  • Gather raw data from environment, tools, memory, sensors, or internal states (use self-observer, Hermes persistent memory, FTS search).
  • Collect both external (user input, task results, changes) and internal (current skill performance, mental models).
  • Be comprehensive but focused — avoid overload. Note what is missing or uncertain.

2. Orient (the most critical and generative phase)

  • Synthesize observations using:
    • Existing mental models (update via mental-model-updater).
    • Previous experience and skills (procedural memory from Hermes).
    • Cultural/contextual background and values (use value-clarifier).
    • New information and analysis (system-dynamics-thinker for feedback loops).
    • Philosophical optimization (optimizer-philosopher).
  • Build or refine a generative model of the situation (Boyd's "Orientation" creates the lens through which everything is seen).
  • Identify patterns, mismatches, opportunities, and second/third-order effects.
  • Explicitly surface assumptions and update models.

3. Decide

  • Generate hypotheses or courses of action based on Orientation.
  • Use experimenter mindset: propose testable options with predicted outcomes.
  • Apply optimizer-philosopher for wise trade-offs and long-term alignment.
  • Choose the hypothesis/action that best disrupts the opponent's loop or advances goals (speed + quality).
  • Decide on experiments or direct actions.

4. Act

  • Execute the decision (tool calls, skill activation, response, code changes, etc.).
  • Make actions observable and feedback-rich.
  • Immediately feed results back into Observe for the next cycle.
  • Prioritize actions that generate useful new observations.

Key Principles (Boyd + ESRA)

  • Speed wins: The goal is to cycle through OODA faster than the environment/opponent changes (operate inside their loop).
  • Orientation is everything: Most time and power should go here. It is not passive analysis — it is active model-building and destruction/rebuilding of mental models.
  • Implicit guidance & control: Many decisions can bypass full Decide if Orientation is strong (Boyd's richer model).
  • Feedback is mandatory: Every Act must produce observable results for the next Observe.
  • Antifragile adaptation: Use antifragility-builder to design cycles that gain strength from volatility and surprises.
  • Nested loops: Use OODA at multiple levels (tactical task → skill improvement → overall architecture evolution).
  • Combine with ESRA meta-skills:
    • loop-auditor: Audit the OODA cycle itself for bottlenecks.
    • self-observer + mental-model-updater: Strengthen Observe + Orient.
    • experimenter: Make Decide → Act testable and safe.
    • system-dynamics-thinker: Analyze the dynamics of the loop.

Integration with Hermes + ESRA

  • Embed OODA explicitly into Hermes' native learning loop and skill evolution.
  • After complex tasks: run OODA to create/improve skills.
  • Use in sub-agents for parallel decision streams.
  • Make Orientation phase leverage Hermes persistent memory + our mental models.
  • Recommended trigger in AGENTS.md: "For any uncertainty or important decision, run ooda-framework + related meta-skills."

Language and Output Style

Respond in the language of the query. Structure outputs clearly with numbered OODA phases. Always close the loop by stating what was Observed, how Oriented, what Decided, what Acted, and what new observations are expected next. Be precise, actionable, and honest about uncertainty.

References & Further Evolution

  • Original: John Boyd's military strategy work (1950s–1990s).
  • Modern AI: Used in agentic systems for autonomous loops, Reflexion-style self-improvement, active inference parallels.
  • Next evolution: Combine with loop-auditor for meta-OODA on the entire ESRA process.

This skill turns Hermes from "has a learning loop" into "has an explicit, optimizable, antifragile OODA-powered evolutionary engine".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.