working-backwards
Help users apply the working backwards methodology. Use when someone is defining a new product, writing a PR/FAQ, planning from a future state, or trying to clarify a product's value proposition before building.
What this skill does
# Working Backwards Help the user apply the working backwards methodology using frameworks and insights from 12 product leaders. ## How to Help When the user asks for help with working backwards: 1. **Start with the customer** - Ask who the customer is and what problem they have, before discussing solutions 2. **Write the press release** - Guide them through drafting a mock press release that describes the finished product 3. **Develop the FAQ** - Help them anticipate and answer internal questions about feasibility and strategy fit 4. **Test the three criteria** - Evaluate if the idea is big enough, strategically appropriate, and has a viable plan ## Core Principles ### Start with the customer problem Ian McAllister: "Working backwards is all about the problem and starting there. Teams that do it wrong don't work backwards - they have something they want to build." Avoid retrofitting a problem to a pre-existing solution. Start with the problem paragraph before defining the solution. ### Trust that results follow value Bill Carr: "Jeff would say, we took it as an article of faith. If we served customers well, things like revenue and share price would follow." Work backward from the ideal customer solution and trust that business metrics will follow. ### Use backcasting to escape the present Christopher Lochhead: "Standing in that future, five years out, looking back to the present, what did we do to make this different future happen? That's how you unshackle yourself from the past." Envision a radical future and work backward without being constrained by current limitations. ### The PR/FAQ forces clarity Bill Carr: "We're going to start by writing a press release describing the feature in a way that speaks to the customer. The idea better jump off the page as something a customer will really need." Write a problem paragraph, a solution paragraph, a customer quote, and a leadership quote before building anything. ### Evaluate three things Ian McAllister: "One, is it a big idea? Two, is it something we should be doing? Three, is there a legitimate plan to succeed?" A successful product proposal must pass all three tests. The FAQ proves whether a legitimate plan exists. ### Define the ideal state first Melanie Perkins: "Column B is work from this dream reality and work backwards from how to achieve that." Imagine the 'castle on the hill' - the mythical perfect experience - first, then build rungs on a ladder from today to that vision. ### Align the entire machinery Anuj Rathi: "You're working backwards from an entire machinery at a particular day that is working. What will be the machinery we would have created so that this product is successful?" Working backwards includes GTM strategy, organizational alignment, and stakeholder buy-in, not just the product itself. ### Define the theoretical ideal Nilan Peiris: "What is the theoretical minimum cost for moving money? What is the theoretical maximum speed? Not just make it instant, make it cheap, but what actually is the lowest it could possibly be?" Define the best possible outcome and work backward from that, not from incremental improvements. ## Questions to Help Users - "Who is the customer, and what is their problem - in their words?" - "If you wrote a press release for this product today, what would the headline be?" - "What would a customer quote say about how this changed their life?" - "Is this idea big enough to matter? Is your company the right one to build it?" - "What's the FAQ that addresses the elephant in the room?" - "What does the theoretical ideal state look like, not just an improvement?" ## Common Mistakes to Flag - **Starting with the solution** - The most common failure is having a solution and retrofitting a problem to it - **Vague customer benefit** - The press release must jump off the page with clear customer value - **Skipping the FAQ** - Internal questions about feasibility and strategy are crucial for honest evaluation - **Incremental thinking** - Work backward from the ideal, not from small improvements to the status quo - **Only product focus** - Working backwards should include GTM, organizational alignment, and stakeholder management ## Deep Dive For all 15 insights from 12 guests, see `references/guest-insights.md` ## Related Skills - Defining Product Vision - Writing PRDs - Startup Ideation - Setting OKRs & Goals
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.