All authors
Claude Skills by envisioning
github.com/envisioning17 skills1 installs9 views
- Adjacency ScanMap where to play next from a defined home position — adjacent categories, customers, geographies, channels, capabilities — one hop out, each anchored in evidence and scored for strategic fit, defensibility and time to entry. Use when the user asks "where could we expand", "adjacent markets", "what's next to our core", "growth options", "adjacency". Stage: sense.Votes: 0GitHub stars: 2
- Artifact From The FutureRender a signal, scenario or idea as a concrete object from a future date — a press release, product page, news headline set, regulator's notice, support ticket, obituary, onboarding email — in the voice of that world, so a team can react to it. Design fiction, disciplined. Use when the user asks for "a press release from 2035", "what would the headline be", "show me what this looks like", "design fiction", or needs a workshop provocation. Stage: make.Votes: 0GitHub stars: 2
- Competitive ScanTrack the observed moves of a named competitor set within a category — product, pricing, GTM, hiring, funding, messaging — grounded in the competitors' own filings, pages and postings, scored for threat, momentum and confidence. Use when the user says "what are competitors doing", "competitive scan", "track rivals", "battlecard input", or names companies and asks what they are up to. Stage: sense.Votes: 0GitHub stars: 2
- FramesSynthesize a set of signal cards into frames — named narrative groupings such as drivers of change, tensions, or emerging themes — each with a title, summary, body and the signals it binds, many-to-many. Use when the user asks "what are the themes", "drivers of change", "cluster these signals", "what's the story here", "frames", or needs the layer between raw signals and a report. Stage: structure.Votes: 0GitHub stars: 2
- Grill The FutureInterrogate a plan, strategy, roadmap, pitch or spec for the bets it silently makes about the future — timelines, adoption, regulation, substitutes, "this stays true" — and score each by fragility. Relentless, one question at a time. Use when the user says "grill", "stress-test", "what am I assuming", "poke holes", "pre-mortem", or shares a plan and wants it challenged. Stage: stress.Votes: 0GitHub stars: 2
- GroundVerify a signal against primary sources — search for evidence, judge each source as supports / contradicts / unrelated, then issue a grounding state (verified, rejected, pending) with confidence and a written rationale. Use when the user asks "is this real", "verify this signal", "find sources for", "ground this", "how solid is this", or after any scan. Stage: sense.Votes: 0GitHub stars: 2
- Horizon ScanRun a STEEP horizon scan on a topic or domain: surface weak signals of change across social, technological, economic, environmental and political layers, merge duplicates, ground each in primary sources, score impact, and write a scan index. Use when the user says "horizon scan", "scan the macro environment", "weak signals on", "what is changing around X", or needs input for scenario or board work. Stage: sense.Votes: 0GitHub stars: 2
- ImplicationsCascade the consequences of a change — first, second and third order — as a futures wheel, with who is affected at each ring and where the cascades collide. Use when the user asks "what happens if", "what are the implications", "second-order effects", "knock-on effects", or has signal cards and wants to see what they lead to. Stage: structure.Votes: 0GitHub stars: 2
- Innovation RadarSpot emerging practices, business models and operating patterns — not raw technology — that change how value is created in an industry or function, with named practitioners, scored for novelty, adoption momentum and strategic fit. Use when the user asks "how are others doing this differently", "new business models in", "innovation radar", "emerging practices", "who is reinventing X". Stage: sense.Votes: 0GitHub stars: 2
- MergeDeduplicate a set of signal cards — find near-duplicates that describe the same underlying development, keep the most specific title, preserve the stronger evidence, and freeze the duplicates with a pointer instead of deleting them. Use when the user says "dedupe these", "merge duplicates", "these overlap", "clean up the scan", or after generating cards from several sources. Stage: structure.Votes: 0GitHub stars: 2
- Regulatory ScanTrack rulemaking, enforcement, court rulings, self-regulation and standards activity for a named jurisdiction and topic, grounded in primary regulator sources, scored for compliance impact, time to effect and jurisdictional breadth. Use when the user asks "what regulation is coming", "regulatory scan", "compliance landscape", "is there a rule on", "what has the regulator done about". Stage: sense.Votes: 0GitHub stars: 2
- ReportWrite a narrative report from a scan's active signals and frames, shaped by a report type — executive readout, board narrative, watchlist, compliance memo, or a custom type — in house voice, with every claim traceable to a card. Use when the user says "write it up", "executive summary of the scan", "report for leadership", "turn this into a memo", "board slide notes". Stage: make.Votes: 0GitHub stars: 2
- Risk RadarSurface downside indicators — incidents, precursors, advisories, hazards — across a defined exposure surface: operational, geopolitical, supply chain, cyber, climate-physical, reputational; grounded in agency advisories and incident reports, scored for likelihood, severity and horizon. Use when the user asks "what could hit us", "risk radar", "emerging threats to", "what should risk be watching", "supply chain risks for". Stage: sense.Votes: 0GitHub stars: 2
- ScenariosBuild a 2x2 scenario set from a topic or a set of signals — extract critical uncertainties, pick the two that matter, name four scenarios, and give each one tells and a strategic posture. Use when the user asks "what could happen", "scenarios for", "possible futures", "how might this play out", or wants to plan against uncertainty rather than a forecast. Stage: project.Votes: 0GitHub stars: 2
- ScopeTurn a vague foresight request into a briefing — the decision it serves, the boundary, the horizon, the audience, what's out, and which playbook fits — by asking a few questions and writing the answers down before any scanning starts. Use when the user says "we want to look at the future of X", "scope this", "set up a scan", "what should we research", or when any scan skill is invoked without a clear boundary. Stage: sense (before it).Votes: 0GitHub stars: 2
- SignalTurn a URL, article, paper, note or observation into a structured signal card — STEEP, technology, maturity, direction, so-what, tells to watch. Use when the user shares a link or fact and asks "is this a signal", "log this", "what does this mean", or wants a horizon-scanning entry. Stage: sense.Votes: 0GitHub stars: 2
- Technology ScanMap publicly documented technologies inside a defined scope — hardware, software, applications, ethics & security — with readiness level, impact and investment scores, each grounded in open sources. Use when the user asks "what technologies exist for", "technology landscape", "tech scan", "TRL of", "who is building", or wants a radar of capabilities in a field. Stage: sense.Votes: 0GitHub stars: 2