skills/planning-under-uncertainty/SKILL.md
Help users plan products and strategy when outcomes are unpredictable. Use when someone is dealing with ambiguous timelines, building in fast-moving markets, planning AI/ML projects, or asking how to make commitments when they don't know what will happen.
npx skillsauth add cvillamarp-lgtm/skillspodcast planning-under-uncertaintyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user navigate product planning when the future is unclear using adaptive planning frameworks from 44 product leaders.
When the user asks for help with planning under uncertainty:
Amjad Masad: "Being agile, not being stuck with roadmaps, being able to just say, oh, we're just going to switch priorities right away, is going to be super important." In rapidly changing environments like AI, maintain flexibility to pivot when new capabilities emerge rather than committing to rigid long-term plans.
Upasna Gautam: "Any time we're planning we build in buffers for all of that chaos that's happening on a daily basis." In chaotic environments, planning must include explicit time buffers and contingency plans ranging from days to months depending on scope.
Shaun Clowes: "Data is more like a compass than a GPS. If you look at data as a way of giving you the answer, you're always wrong." Use data to validate or invalidate intuition rather than waiting for it to tell you exactly what to do.
Ramesh Johari: "Experimentation was never historically in science about winners and losers... Experimentation is always very hypothesis driven. It's about, what are you learning?" A healthy experimentation culture values learning from "failed" risky bets more than safe, incremental "wins."
Nikita Bier: "Develop a reproducible testing process, and that will actually influence the probability of your success more than anything." Success in uncertain markets is driven by the quality and speed of the testing process rather than the initial idea.
Alex Hardimen: "There's this incredible humility that was needed to really understand and first diagnose what was actually happening on the platform." Managing through a crisis requires "wartime" humility to accurately diagnose problems before attempting solutions.
Eric Ries: "Give yourself a fixed period of time to take some decisive action and see if it feels better." Build checkpoints into plans where you'll reassess based on what you've learned, not just calendar dates.
Claire Hughes Johnson: "Type one, type two decisions. Is it high impact? Is it irreversible? Is it not?" Spend more time on one-way doors and move quickly on reversible decisions that can be adjusted later.
For all 52 insights from 44 guests, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.