Classify a problem using Cynefin triangulation before acting — routes to the right skill chain (investigate, brainstorm, probe, troubleshoot).
89
89%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
🎯 Complex → Probe → /brainstorm → /probe | OpenSpec: yes | Scale: {scale}
From: Confused → To: Complex Constraint shift: unknown → enabling. Problem has no clear cause-effect; need divergent exploration to surface hypotheses before probing.
probe needs testable claimsprobe, not implementationToken guidance: target 300 tokens inline. For depth, use references — point to thinking artifact files rather than embedding full content. Soft cap: 600 tokens inline per handoff. If you need more, move detail to a knowledge file and reference it. Accumulated cap: 800 tokens across a chain — compress to 200 at cap (keep: decisions, constraints, rejected paths). References to thinking files do NOT count toward the cap.