working-backwards

Apply Working Backwards to draft PR/FAQs and plan from a future state.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/PSkinnerTech/lenny-skills --skill working-backwards-pskinnertech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: working-backwards
Source: https://github.com/PSkinnerTech/lenny-skills/tree/main/skills/working-backwards
Command: npx skills add https://github.com/PSkinnerTech/lenny-skills --skill working-backwards-pskinnertech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Working Backwards skill guides teams to define problems from the customer’s perspective, draft PR/FAQs, and plan from a future state before building.

Core Features & Use Cases

  • Start with the customer problem and write a clear problem paragraph to anchor the idea.
  • Draft a PR/FAQ with problem, solution, customer quote, and leadership quote to force clarity.
  • Define the ideal future state and backcast practical steps, aligning GTM, organization, and strategy.

Quick Start

Draft a future-state press release and a supporting FAQ to anchor your product idea before building.

Frequently Asked Questions about working-backwards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the Working Backwards methodology for product strategy?

The Working Backwards methodology starts by defining the customer problem, then drafting a future-state press release and FAQ to force clarity, and finally backcasting practical steps to align strategy and delivery.

How do I draft a PR/FAQ to align cross-functional teams before building?

To draft a PR/FAQ, write a clear customer problem paragraph, outline the proposed solution, and include simulated customer and leadership quotes to force clarity and align cross-functional teams.

When do I need to write a future-state press release for product proposals?

You need a future-state press release when you must anchor a product idea, validate the ideal future state, and check GTM, compliance, and strategy alignment before committing engineering resources.

Can I use this working backwards approach for cross-functional alignment checks?

Yes, working backwards supports cross-functional alignment checks by using PR/FAQ artifacts and future-state storytelling to validate proposals across GTM, compliance, organization, and strategy.

What is the best way to define customer problems before building a product?

The best way is to write a clear problem paragraph from the customer's perspective, then draft a PR/FAQ and backcast practical steps from the ideal future state to ensure legitimate product planning.

Does working backwards require any specific dependencies to plan from a future state?

No dependencies are required, making it straightforward to start backcasting practical steps and building legitimate plans from a future state without prior technical environment setup.