IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this.

How to Access Skills

In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.

Using OAC Skills

The Rule

Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.

digraph skill_flow {
    "User message received" [shape=doublecircle];
    "About to build/create something?" [shape=doublecircle];
    "Already brainstormed?" [shape=diamond];
    "Invoke oac:approach skill" [shape=box];
    "Might any OAC skill apply?" [shape=diamond];
    "Invoke Skill tool" [shape=box];
    "Announce: 'OAC skill loaded: [friendly-skill-name] — [purpose]'" [shape=box];
    "Has checklist?" [shape=diamond];
    "Create TodoWrite todo per item" [shape=box];
    "Follow skill exactly" [shape=box];
    "Respond (including clarifications)" [shape=doublecircle];

    "About to build/create something?" -> "Already brainstormed?";
    "Already brainstormed?" -> "Invoke oac:approach skill" [label="no"];
    "Already brainstormed?" -> "Might any OAC skill apply?" [label="yes"];
    "Invoke oac:approach skill" -> "Might any OAC skill apply?";

    "User message received" -> "Might any OAC skill apply?";
    "Might any OAC skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
    "Might any OAC skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
    "Invoke Skill tool" -> "Announce: 'OAC skill loaded: [friendly-skill-name] — [purpose]'";
    "Announce: 'OAC skill loaded: [friendly-skill-name] — [purpose]'" -> "Has checklist?";
    "Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
    "Has checklist?" -> "Follow skill exactly" [label="no"];
    "Create TodoWrite todo per item" -> "Follow skill exactly";
}

Available OAC Skills

Skill Priority

When multiple skills could apply, use this order:

1. Process skills first (approach, debugger) — these determine HOW to approach the task
2. Implementation skills second (context-discovery, task-breakdown, code-execution) — these guide execution

"Let's build X" → approach first, then context-discovery, then implementation skills. "Fix this bug" → debugger first, then verification-before-completion.

Red Flags

These thoughts mean STOP — you're rationalizing:

Skill Types

Rigid (debugger, verification-before-completion): Follow exactly. Don't adapt away discipline.

Flexible (approach, context-discovery): Adapt principles to context.

The skill itself tells you which.

Skill Friendly Names

When announcing a skill, use the friendly name below (not the internal skill ID):

Example announcement: OAC skill loaded: OAC Approach — planning before implementation

User Instructions

Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.