Change Sequence Issues
I am stuck at a resistance layer
Section titled “I am stuck at a resistance layer”This is not a bug. The layer IS the work.
Stuck at Layer 3 (direction) means the proposed direction does not feel right — that is important information, not a failure. Stuck at Layer 5 (negative ramifications) means a real concern has not been adequately addressed.
Tell the system specifically what worries you.
If you genuinely cannot move:
- Re-read
.claude/rules/change-sequence.mdin your own system - Ask: “Explain what Layer [X] means and what resolution looks like”
- Bring it to office hours if you are a 90MM member
- Consider that being stuck might mean the direction needs to change. That is the process working, not failing.
The system keeps jumping to execution
Section titled “The system keeps jumping to execution”It should not. If it is proposing action items before completing the EC, FRT, NBR, and S&T Tree, tell it:
“We haven’t completed the change sequence yet. Where are we in the sequence?”
It will check the status in CLAUDE.md and return to the right step.
The Evaporating Cloud does not make sense
Section titled “The Evaporating Cloud does not make sense”The EC can feel abstract the first time. Ask: “Walk me through the conflict in simpler terms.”
It should restate the cloud in your own language and your specific situation rather than framework terminology. If it is still unclear, The Three Questions explains what the EC does and why.
The activation inventory is overwhelming
Section titled “The activation inventory is overwhelming”Common, and not a problem. Say:
“This is too much. What’s the minimum viable version that still addresses the constraint?”
The system will help you find the smallest version that still works. You can always expand later — and a small plan you execute beats a complete one you do not.