One-click install
npx skills add https://github.com/HMWKR/claude-code-skills --skill ooda-hmwkr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ooda
Source: https://github.com/HMWKR/claude-code-skills/tree/main/skills/ooda
Command: npx skills add https://github.com/HMWKR/claude-code-skills --skill ooda-hmwkr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running tasks frequently drift off course when context shifts, new requirements emerge, or unexpected issues (like test failures) arise mid-execution, leading to wasted effort on outdated plans and misaligned outcomes.

Core Features & Use Cases

  • Structured OODA Loop Workflow: Guides you through the Observe-Orient-Decide-Act cycle to objectively assess progress, update your mental model with new information, and make informed plan adjustments.
  • Automatic Checkpoint Triggers: Runs lightweight progress checks after 5+ conversation turns, test/build failures, or explicit user feedback to catch drift early without manual prompting.
  • Safe Plan Adjustment Guardrails: Requires explicit user confirmation before making strategic direction changes, preventing unapproved pivots that derail work.
  • Use Case: Ideal for mid-development workflow adjustments, responding to sudden requirement changes, or validating that your current approach is still on track after unexpected setbacks.

Quick Start

Invoke the ooda skill when you need to check progress on a long-running task or adjust your plan after unexpected changes.

Frequently Asked Questions about ooda

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent task drift in long-running development workflows?

To prevent task drift in long-running workflows, use an adaptive execution cycle that implements structured progress observation and automatic checkpoints after 5+ turns, test failures, or user feedback.

What is the OODA Loop process for software development tasks?

The OODA Loop process for development tasks guides you through Observe, Orient, Decide, and Act phases to objectively assess progress, update mental models with new information, and adjust plans mid-execution.

How do I adjust a project plan after unexpected test failures or requirement changes?

You adjust a project plan after failures by triggering a progress checkpoint, orienting to the new context, and requiring explicit user confirmation before making strategic direction changes to ensure safe plan adjustment.

When should I run progress tracking checks during a long task?

You should run progress tracking checks automatically after 5+ conversation turns, immediately following test or build failures, or whenever explicit user feedback suggests your current approach might be drifting.

Can I pivot my execution strategy without losing my original task context?

Yes, you can pivot execution strategy safely because the workflow requires explicit user confirmation before applying strategic direction changes, ensuring your original task context and mental model are updated rather than discarded.