signpost-trackerlisted

Designs the early-warning indicators for each scenario, with thresholds and a review cadence, and runs the quarterly re-scan and review so the scenarios and the roadmap stay alive after the workshop, part of the Creative Futurology Pack by Polar Bear. Use this whenever the user says "run signpost-tracker", "which future are we in now", "set up the early warning indicators", "quarterly scenario review", "has anything changed since the offsite", or when it is three months later and someone wonders whether the scenarios still hold. Use it even for "should we be worried about anything yet".
polar-bear-org/claude-skills · ★ 1 · AI & Automation · score 62

Install: claude install-skill polar-bear-org/claude-skills

# Signpost Tracker Scenarios die of neglect, not of being wrong. A set built in March is quietly obsolete by November unless someone is watching for the signs that were written into it, and "someone" without a cadence and a checklist is nobody. A signpost is an observable event or measure that would tell you a particular world is forming: a regulator publishing final rules, a third client in a quarter asking for a rate card, a named competitor announcing an in-house studio. Signposts are chosen from the scenarios' early signs and the signal log, they have thresholds (how much, how many, by when), and they are reviewed on a date in the calendar, with the roadmap's triggers wired to them. The discipline here is honest reading. A quarterly review that finds "all our signposts are moving toward the world we planned for" is usually a review that looked at the friendly signposts first. So I make you look at the others. ## How to work with me Run me twice. First, right after implications-roadmap-builder, in a chat pinned "signposts setup", to design the indicator set. Then every quarter (or whatever cadence you set), in a chat pinned "signposts Q1", "signposts Q2", and so on, with a fresh signal-scanner round before it. The design takes me an hour; a quarterly review takes me an hour and the team a 45-minute meeting. ## Before starting For the design run, I read `scenarios-[slug].md` (early signs per world), `roadmap-[slug].md` (the bets and their triggers), and `signals-[slug]