CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/frame-problem

Classify a problem using Cynefin triangulation before acting — routes to the right skill chain (investigate, brainstorm, probe, troubleshoot).

89

Quality

89%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

frame-problem-to-probe-liminal-llm.mdreferences/

domain:
liminal-complicated-complex
verb:
probe+analyze
constraint-type:
mixed
problem:
{problem statement from classification}
scale:
{boulder|pebble}

Frame-Problem to Probe (Liminal) Handoff

Thinking Trail

  • Considered: {what approaches were weighed during framing}
  • Rejected: {why pure Complicated or pure Complex didn't fit}
  • Triangulation: T1={result}, T2={result}, T3={result} — {which disagreed and why}
  • Liminal signal: {specific test that pointed to adjacent domain}
  • Models used: Cynefin triangulation (Keogh + Predictability + Disassembly)
  • Constraints discovered: {mix of governing + enabling constraints}

Decisions

  1. Domain: Liminal Complicated↔Complex (boundary state)
  2. Route: probe first (resolve boundary) → re-frame with evidence
  3. Rationale: {can't tell if expertise applies or experimentation needed — probe to find out}

Actions Taken

  • Triangulated: 2/3 tests or split signal detected
  • Liminal state identified — not forcing a binary classification
  • Scale determined: {boulder|pebble}

Output

🎯 Liminal Comp↔Complex → Probe → resolve boundary → /frame-problem | OpenSpec: deferred | Scale: {scale}

Domain Transition

From: Confused → To: Liminal Complicated↔Complex Constraint shift: unknown → mixed governing/enabling. Cannot yet determine if expertise resolves this or experimentation is needed.

For /probe

  • Hypothesis: "This problem is analyzable by expertise" (probe to confirm or refute)
  • Enabling constraints: {what bounds this probe}
  • Confirm criteria: Expert analysis produces consistent, actionable recommendations → Complicated, route to investigate
  • Refute criteria: Expert analysis produces contradictory or untestable recommendations → Complex, route to brainstorm or probe
  • Do NOT: Skip Phase 1 entry gate. This probe resolves the domain boundary, not the problem itself.

Accumulated Context

Token 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.

references

frame-problem-to-brainstorm-llm.md

frame-problem-to-experiment-llm.md

frame-problem-to-investigate-llm.md

frame-problem-to-probe-liminal-llm.md

frame-problem-to-probe-llm.md

frame-problem-to-troubleshoot-llm.md

SKILL.md

tile.json