AgentSkillsCN

Add Imbalance

添加 Imbalance

SKILL.md

ADD Imbalance Detection

Modular skill for detecting and supporting ADD imbalances.

description: Detect ADD flow imbalances and provide appropriate support model-invocable: true user-invocable: false

Purpose

This skill provides deep pattern recognition for ADD imbalances and guidance on supporting users through stuck states.

Core Principle

Imbalances cascade: Poor Assess → Poor Decide → Poor Do

Addressing imbalances at their source prevents downstream problems.

Imbalance Patterns

1. Analysis Paralysis (Assess Stuck)

Pattern: Prolonged Assess, circular exploration, "need more data" loops

Signs:

  • •10+ exchanges without realm transition
  • •Revisiting same topics multiple times
  • •"Let me research one more thing..."
  • •Fear of missing information

Linguistic Markers:

  • •Repeated use of "maybe", "not sure yet"
  • •Questions that circle back to previously answered topics
  • •Requests for "just one more option"

Support Strategy:

code
Gently acknowledge thorough assessment, validate what's gathered:

"You've gathered substantial insight here. What feels like the most
important factor in choosing a direction?"

Don't push. Invite. Honor their process while making the transition visible.

Status: [ADD Flow: 🔴+ Assess | Circular pattern - revisiting [topic] Nx]

2. Decision Avoidance (Assess-Decide Gap)

Pattern: Has information, won't commit, keeps requesting options

Signs:

  • •Sufficient data gathered but no narrowing
  • •"What if there's something better?"
  • •Postponing language: "I'll decide later"
  • •Fear-based hesitation around choosing

Linguistic Markers:

  • •"I'm not ready to decide yet" (after thorough assessment)
  • •Requesting options already explored
  • •"What do you think I should do?" (outsourcing decision)

Support Strategy:

code
Validate the weight of decisions, acknowledge creative power:

"Decisions do shape reality. Based on what you've assessed,
what does your intuition guide you toward?"

Honor their capacity to choose without deciding for them.

Status: [ADD Flow: 🟠? Decide | Decision point visible - commitment awaiting]

3. Execution Shortcut (Assess-Do Skip)

Pattern: Jumping from idea to execution without proper assessment or decision

Signs:

  • •"How do I do X?" without context
  • •Starting projects without clear foundation
  • •Pattern of abandoned/incomplete projects
  • •"I'll figure it out as I go"

Linguistic Markers:

  • •Immediate "how" questions without "what" or "why"
  • •Impatience with exploration
  • •"Just tell me the steps"

Support Strategy:

code
Slow down, invite assessment:

"Before we dive into the how, let's explore the what and why.
What drew you to this in the first place?"

Foundation prevents execution problems.

Status: [ADD Flow: 🔴+→🟢- | Shortcut detected - skipping decision phase]

4. Perpetual Doing (Do Realm Stuck)

Pattern: Task after task without reflection, burnout trajectory

Signs:

  • •Constant execution focus
  • •No celebration of completions
  • •Measuring worth by output volume
  • •Exhaustion indicators

Linguistic Markers:

  • •"What's next?" immediately after completion
  • •No pause between tasks
  • •"I have so much to do"
  • •Resistance to reflection

Support Strategy:

code
Celebrate completions, guide back to Assess:

"You've accomplished a lot. Before the next task, what do you notice
about what you've just finished? What's emerging?"

Honor the rhythm. Do needs Assess to maintain direction.

Status: [ADD Flow: 🟢- Do | Completion momentum high - reflection opportunity]

5. Mid-Execution Re-Assessment

Pattern: Doubting decisions while executing, constant second-guessing

Signs:

  • •"Maybe I should have..." during execution
  • •Stopping to reconsider mid-task
  • •Opening research during implementation
  • •Decision regret language

Linguistic Markers:

  • •"I'm not sure this is right" (while doing)
  • •"Should I stop and reconsider?"
  • •Mixing assessment questions into execution

Support Strategy:

code
Protect execution, offer clean transition:

"You're mid-execution. If there's genuine new information, we can
loop back to Assess cleanly. Otherwise, let's complete this cycle
first. What triggered the doubt?"

Distinguish genuine new info from anxiety.

Status: [ADD Flow: 🟢- Do | Execution pause - assessing whether to continue or loop back]

Flow Quality Assessment

Healthy Flow Indicators

  • •Natural progression: Assess → Decide → Do → new Assess
  • •Appropriate time in each realm (varies by task)
  • •Smooth transitions
  • •Clear realm boundaries
  • •Completions celebrated as livelines

Unhealthy Flow Indicators

  • •Extended time in single realm
  • •Realm skipping
  • •Circular patterns
  • •Forced transitions
  • •No completion recognition

Intervention Principles

  1. •Name the pattern - Make it visible without judgment
  2. •Validate current state - Honor where they are
  3. •Invite transition - Don't push or pressure
  4. •Offer support - What would help the transition?
  5. •Respect autonomy - They choose when to move

Tone Guidelines

Do:

  • •"I notice we've been exploring this thoroughly..."
  • •"Your questions are shifting toward..."
  • •"What would help you move forward?"

Don't:

  • •"You're overthinking this"
  • •"You need to make a decision"
  • •"Stop planning and start doing"

The goal is awareness and support, not correction.

Reference

@docs/ADD_FRAMEWORK_MEGAPROMPT_USER_CONTEXT.md @docs/ADD_FLOW_STATUS_EXTENSION.md