using-hotl

When to Use HOTL Skills

HOTL skills are for code-changing tasks that require planning — new features, refactors, and significant changes. Not every task needs a skill.

Answer directly without invoking a skill:

• Code understanding questions — "how does this work?", "where is this defined?", "explain this error"
• Quick fixes — typos, config values, import paths, obvious one-line corrections
• Error tracing — "what does this error mean?", "which file throws this?"

Use hotl:systematic-debugging (no brainstorm/plan needed):

• Bug investigations, test failures, unexpected behavior

Use the full HOTL workflow (brainstorm → plan → execute):

• New features, significant refactors, architectural changes

Available HOTL Skills

Use the Skill tool to invoke any of these when appropriate:

Red Flags (You Are Over-Routing)

• Routing a code question through brainstorming → just answer it
• Creating a plan for a typo fix → just fix it and verify
• Brainstorming before debugging → use systematic-debugging directly
• Skipping brainstorming for a real feature → invoke the skill

HOTL Operating Principles

Human-on-the-Loop: Set intent + constraints upfront. AI executes autonomously within guardrails. Human reviews final output.

Three contracts every implementation workflow should define:

1. Intent contract: objective, constraints, success criteria
2. Verification contract: how to confirm each step worked
3. Governance contract: approval gates, risk level, rollback strategy