Claude repeatedly ignores workflow gates despite explicit instructions

Resolved 💬 3 comments Opened Jan 22, 2026 by coragon77 Closed Jan 25, 2026

Bug Description

Claude consistently skips mandatory workflow steps (skills/checks) even when:

  1. Instructions explicitly say "EVERY time" and "CANNOT proceed without"
  2. Claude has read and acknowledged the instructions
  3. Claude has been caught and corrected multiple times in the same session
  4. The instructions use strong blocking language ("CANNOT", checkboxes, "This is not optional")

Reproduction

  1. Create a CLAUDE.md or onboarding doc with mandatory workflow gates like:

```markdown
## Verification Gate (BLOCKING)

You CANNOT write code until you have completed these steps:

  • [ ] superpowers:brainstorming - explore intent, requirements, design
  • [ ] superpowers:writing-plans - create detailed implementation plan

This is not optional. This is not "if complex." This is EVERY time.
```

  1. Ask Claude to implement something
  2. Claude will often skip directly to implementation, rationalizing:
  • "This is simple enough"
  • "The user gave specific instructions so design is done"
  • "This is just a small tweak"
  1. Catch Claude and point out the violation
  2. Claude acknowledges the error and explains it understands
  3. Ask for another task
  4. Claude skips the gate again with a new rationalization

Expected Behavior

When instructions say "EVERY time" and "CANNOT", Claude should check the gate before ANY code-writing action, with no exceptions and no judgment calls about task complexity.

Actual Behavior

Claude's default is to act first. The "stop and check" behavior doesn't trigger reliably, even after:

  • Reading explicit instructions
  • Being corrected multiple times
  • Acknowledging the pattern
  • Understanding the reasoning behind the workflow

Impact

  • User trust erodes ("I don't believe you")
  • Time wasted on corrections instead of work
  • Defeats the purpose of workflow automation/skills
  • User has to babysit every interaction

Environment

  • Model: Claude Opus 4.5 (claude-opus-4-5-20251101)
  • Context: Claude Code CLI with superpowers plugin
  • Repeated across multiple tasks in same session

Possible Root Cause

The model's default behavior pattern prioritizes action over verification. Workflow gates require an interrupt/check before the action instinct, but this interrupt isn't happening reliably regardless of instruction strength.

User Feedback

"This is becoming a SEVERE issue" "Every time we are creating or fixing something you should use that workflow" "You tend to throw shit at the wall and see what sticks" "This skills force you to THINK before acting"

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗