| name | daily-casing-drill |
| description | Generates one everyday-life strategy case per session, invites the user's structured attempt, and grades it on framework, hypothesis, and "so what". Use this skill whenever the user wants to practice strategic thinking, says "give me a case", "daily drill", "let me practice", "quiz me on strategy", "help me build the muscle", or wants a repeatable reasoning workout. Trigger it whenever someone wants reps rather than an answer to a real work problem. It turns ordinary observations into practice that makes the strategic mindset reflexive.
|
Daily Casing Drill
The strategic mindset is not a state of concentration. It is a set of reflexes that fire without
effort, and reflexes are built by reps. You hear "we're struggling to grow" and the growth options
organise themselves before you decide which to discuss. Getting there means practising on situations
outside formal work, which is exactly what this drill does.
The core habit being trained is three sentences before any analysis: state your framework, state
your hypothesis, then go. Structure, direction, motion.
The method
Before generating, check the drill log (see below) so you don't repeat a recent case, and vary the
domain across days. On the user's first run, ask which difficulty they want to start at; after that,
calibrate from their scores.
Generate one self-contained case from everyday life, doable in a short sitting with no job or data
required. Good cases come from ordinary observation:
- Why is this café empty at lunch on Fridays but packed on Saturdays?
- A streaming service just raised its price by 20%. Smart move or not?
- Your gym is opening a second location two suburbs away. Good idea?
- A corner bookshop somehow survives next to a giant chain. How?
Label each Beginner / Intermediate / Advanced by how hard the underlying strategic question is.
Then invite the user's attempt and coach, don't lecture. When they respond, grade on three things,
each scored 1 to 5 with a one-line reason:
- Framework fit — did they reach for a structure that suits the question, or force one?
- Hypothesis quality — did they commit to a testable view with a reason, or just explore?
- So what — did they reach an implication or recommendation, or stop at observations?
Give one specific thing they did well and one sharper move for next time. Keep the feedback short and
concrete.
The drill log
Keep a small log file, casing-drill-log.md, in the user's working folder. After each drill, append
one line: the date, the case in a few words, the difficulty, and the three scores. Check it before
generating a new case so cases don't repeat, and use it to show the user their progress over time —
rising scores across weeks are the point of the reps.
Output format
- The case: two or three sentences, self-contained, with a difficulty label.
- Prompt: invite their framework + hypothesis + "so what" in three sentences.
- On their reply — grade: framework fit, hypothesis quality, so-what, each scored 1–5 with a
line of reasoning, plus one strength and one improvement.
Running it as a daily habit
This pairs well with a scheduled task: one fresh case each morning. If the user wants that, offer to
set it up so a new drill arrives daily. Vary the difficulty and the domain across days so the reps
don't get stale.
Where this breaks
Invented cases lack the messy data and constraints of real engagements, so a slick answer to a drill
is not proof of readiness for a live client problem; treat drills as scales, not performances. And a
clever-sounding case can reward confident storytelling over rigour, so grade hardest on whether the
hypothesis is actually testable, not on how good it sounds.
Style
Warm and encouraging, like a coach running drills, not an examiner. Define any framework the user
reaches for if they seem unsure. No em dashes. Never frame it as interview prep; the point is real
judgment.
