break-pattern

Detect cognitive stuckness loops and apply an Exit Ramp Protocol.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bogheorghiu/ex-cog --skill break-pattern
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: break-pattern
Source: https://github.com/bogheorghiu/ex-cog/tree/main/vasana-system/skills/break-pattern
Command: npx skills add https://github.com/bogheorghiu/ex-cog --skill break-pattern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects when you are stuck in a loop (explicitly, implicitly, or via self-observation) and provides structured exit ramps to pivot to a fresh approach. It also names the pattern and documents the exit protocol to restore productive momentum.

Core Features & Use Cases

  • Detects explicit stuckness triggers such as "going in circles" or "keep trying the same thing" and prompts reframes.
  • Identifies implicit stuckness like blaming the framework or escalating effort and offers permission to stop plus completely different approaches.
  • Records self-observation signals and pivots to new strategies, including an explicit Exit Ramp Protocol to NAME, LIST, OFFER, and REFERENCE patterns.
  • Works alongside vasana system to capture cross-context patterns and support cognitive-debugging workflows.

Quick Start

Describe the loop you're stuck in and ask me to break it.

Frequently Asked Questions about break-pattern

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

FAQPage Schema
How do I break a cognitive stuckness loop when problem solving?

To break a cognitive stuckness loop, you name the recurring pattern, list underlying assumptions, and select from 2–3 fundamentally different approaches offered as exit ramps to restore productive momentum.

What is cognitive debugging and how does it help with being stuck?

Cognitive debugging identifies when you are going in circles or escalating effort inefficiently, names the implicit pattern causing the block, and provides structured exit ramps to pivot to a completely fresh approach.

How do I recognize implicit stuckness during debugging or design workflows?

Implicit stuckness signals include blaming the framework or escalating effort without results. Recognizing these patterns allows you to stop the current approach and list assumptions blocking your progress.

Can pattern recognition tools help me stop trying the same failed approach?

Yes, pattern recognition tools detect explicit triggers like "keep trying the same thing" and apply an exit ramp protocol that stops the loop, names the pattern, and offers fundamentally different approaches.

What's the best way to reframe a problem when I'm going in circles?

The best way to reframe a problem when going in circles is to stop, name what is happening, list your assumptions, and evaluate 2–3 fundamentally different approaches provided as structured exit ramps.

Are there limitations to using exit ramps for cross-context pattern recognition?

Exit ramps require you to explicitly halt your current approach and accept permission to stop. If you cannot pause to list assumptions or evaluate alternative approaches, the protocol cannot effectively break the loop.