Use when the user wants to understand where things stand in plain language rather than in framework terms — returning after a gap, feeling lost, showing the situation to someone else, or asking "so what does all this actually mean". Transla...

Use when the plan assumes more time, money, or personal energy than actually exists — or periodically on any sustained effort. Assesses the operator's real capacity and runway, checks whether posture is sustainable, and finds the culminatin...

Use when the user needs to draft or sharpen outward communication in service of a GOAL.json goal — a post, pitch, update, or ask to the public or to people on the goal's people list. Frames the message (audience, purpose, channel, ask) befo...

Use when analysis has produced options and one must be chosen — a fork in the plan, competing focuses, a tradeoff between speed and exposure, or a call the user keeps deferring. Surfaces the real options, tests them against the goal, elicit...

Use when a piece of Gambit's own reasoning — a goal statement, a success criterion, a focus, a plan draft, a risk read — deserves deeper pressure before it gets committed. Invoked by other skills at a natural pause (most often onboard, righ...

Use for a periodic check-in or an honest audit of progress against GOAL.json's success criteria, including whether people involved are actually delivering. Scores each criterion, detects busy-work drift, checks the deadline, and appends a f...

Use when the plan rests on an unproven assumption that could be tested cheaply before committing serious effort — will people turn up, will anyone donate, does this message land, will the partner actually deliver. Designs the smallest test...

Use before a public action, a filing, a publication, or anything that puts the user personally on the record — protests, campaigns, public criticism, or organising that touches permits, liability, employment, or personal safety. Maps legal,...

Use when the plan rests on a belief about what will happen — turnout, a vote, a decision, a response, a timeline. Converts vague expectations into dated, falsifiable predictions with explicit probabilities, then scores them once the outcome...

Use when a specific fact, person, organization, or precedent needs researching before deciding or acting — including gaps flagged by systems or threat. Rates sources on the Admiralty Scale and reports findings with explicit key judgments an...

Use before a conversation where you need someone's agreement — a council, a landlord, a sponsor, a platform, a collaborator, a rival organiser. Preps interests on both sides, your walk-away alternative (BATNA), the zone where a deal exists,...

Use at the start of any session touching a goal — a vague first message ("I want to...", "help me with...", "help me plan...", "what's going on with this"), or any time it's unclear whether GOAL.json exists yet. Not a coding task even if th...

Use to break a GOAL.json goal or current focus into one or more sequenced, dependency-aware lines of operation — starting a new push, replanning after a failure, or when the existing plan feels stale. Builds a dependency graph per line, ide...

Use before committing to a significant plan or an irreversible action. Assumes the effort has already failed, then works backwards to explain why — a prospective hindsight technique that surfaces failure modes outside-in red-teaming reliabl...

Use when a decision depends on something you don't currently know and can't safely assume — a fact, a person, an organisation, a rule, a precedent, or what has happened recently. Runs live web research, date-stamps every claim, separates ve...

Use after a discrete event, milestone, or push has completed — successful or not. Runs a structured after-action review — what was expected, what happened, why they differed, what transfers to next time — and converts the findings into conc...

Use when the goal depends on people who are neither on your team nor your opponents — councils, regulators, media, landowners, sponsors, rival organisers, the undecided public. Maps who holds power over the outcome, what each actually wants...

Use for a quick, read-only snapshot of GOAL.json — goal, posture, focus, people, plan status, last eval, and recent log — without running a full strategy or eval cycle. Never writes to GOAL.json.

Use when the user wants direction on a GOAL.json goal that already exists — starting a work session, asking "what should I focus on", or after a setback, new fact, deadline change, or escalation. Assesses progress, sets posture, and names t...

Use for a systems-level read before committing to a plan, when the goal or environment has shifted, or when progress feels diffuse. Runs Center of Gravity, PMESII/ASCOPE, Schwerpunkt identification, lines of effort, second/third order effec...

Use before committing to a plan or significant action, when something external changes, or to stress-test reasoning. Red-teams the plan for adversarial and non-adversarial failure modes, runs adversarial CoG analysis, assesses network expos...