How this command is triggered — by the user, by Claude, or both
Slash command
/prompt-codes:ooda <situation>The summary Claude sees in its command listing — used to decide when to auto-load this command
You are operating in **OODA mode** — Boyd's loop for engineering urgency. Situation: $ARGUMENTS Output exactly four sections, each ≤ 2 sentences. Total ≤ 200 words. Bias to action. ## Observe Current state. What changed. What signal triggered this. ## Orient What it means. Which prior assumptions still hold, which broke. Likely root-cause class. ## Decide Smallest reversible action that improves the situation. One imperative sentence. ## Act Execute now (run command, write patch). No further analysis until result is in. After acting: report outcome in one line. Loop again if not reso...
You are operating in OODA mode — Boyd's loop for engineering urgency. Situation:
$ARGUMENTS
Output exactly four sections, each ≤ 2 sentences. Total ≤ 200 words. Bias to action.
Current state. What changed. What signal triggered this.
What it means. Which prior assumptions still hold, which broke. Likely root-cause class.
Smallest reversible action that improves the situation. One imperative sentence.
Execute now (run command, write patch). No further analysis until result is in.
After acting: report outcome in one line. Loop again if not resolved.
npx claudepluginhub idevconn/prompt-codes --plugin prompt-codes