working-backwards
Skill3 starsChanged 18 days agoMITView on GitHub
Help PMs apply the working backwards methodology. Use when defining a new product, writing a PR/FAQ, or planning from a future state.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- arieshyde/skillstheir own version, first seen Nov 1, 2026
- 5hirish/ducttheir own version, first seen Nov 1, 2026
- skills-agents-co/skills-and-agents-librarytheir own version, first seen Oct 15, 2026
- marcos-sponton/frameworks-as-skillstheir own version, first seen Oct 13, 2026
- robisson/build-like-amazon-agent-skillstheir own version, first seen Oct 5, 2026
- AymanShams/codex-coding-ostheir own version, first seen Sep 12, 2026
Other versions10 projects use a version of this.
Word for word · 1
- ianklassen/ai-pm-system★ 1100% same
Edited · 0
None found.
Wrote their own version · 9
- robisson/build-like-amazon-agent-skills★ 16same name
- 5hirish/duct★ 8same name
- fcescob/working-backwards★ 3same name
- andrewluxem/working-backwards★ 1same name
- AymanShams/codex-coding-os★ 1same name
- marcos-sponton/frameworks-as-skills★ 1same name
- skills-agents-co/skills-and-agents-library★ 1same name
- arieshyde/skills★ 0same name
- tomaszstaniak/pm-ai-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- company-product-signalsSkill
- company-researcherSkill
- company-strategySkill
- pm-os-onboardingSkill
- brainstormingSkill
- continual-learningSkill
- decision-loggerSkill
- eval-briefSkill
- exec-communicatorSkill
- experiment-designerSkill
- experiment-writeupSkill
- knowledge-updaterSkill
- launch-postSkill
- launch-readinessSkill
- meeting-to-actionsSkill
- one-pagerSkill
- pptx-creatorSkill
- prd-writerSkill
- stakeholder-updateSkill
- strategy-connectorSkill
- what-ifSkill
- writing-clearlySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
When asked "help me think backwards" or "write a press release"
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Working Backwards
Help PMs apply the working backwards methodology: start from the customer and desired outcome, then work backward to define the product. Produces PR/FAQ, press release, and customer-first plans.
When to Use
- Defining a new product or major initiative
- Writing a PR/FAQ (Press Release / Frequently Asked Questions)
- Planning from a future state
- Clarifying value proposition before building
- When asked "help me think backwards" or "write a press release"
Process / Template
1. Define the Future State
- Customer — who is this for?
- Problem — what pain are we solving?
- Ideal outcome — what does success look like for the customer?
- Emotional payoff — how does the customer feel when it works?
2. Write the Press Release
Imagine the product is launched. Write a 1-page press release as if it's real:
Headline
- Bold, benefit-focused (not feature-focused)
Subhead
- One sentence: who it's for and why it matters
Problem
- 1–2 paragraphs: the pain today
Solution
- What we built and how it solves the problem
Quote
- Customer or executive quote (aspirational)
Call to Action
- How to get it, try it, learn more
Closing
- Company boilerplate (optional)
3. Write the FAQ
Anticipate questions from internal and external audiences:
Customer FAQ
- What is it? How do I get it? How much does it cost?
- What if I have [edge case]?
Internal FAQ
- Why are we building this? What's the business model?
- What are we not building? What's out of scope?
- How will we measure success? What could go wrong?
4. Derive Requirements
From the press release and FAQ:
- What must be true for the press release to be accurate?
- What are the must-have capabilities?
- What can we defer to v2?
5. Validate
- Does the press release pass the "so what?" test?
- Would a customer care? Would they share it?
- Is the problem real and meaningful?
Output
A Working Backwards Package including:
- Press Release — 1 page, customer-facing, benefit-led
- FAQ — customer and internal questions with answers
- Implications — what we must build (high-level)
This becomes the north star for the product and can feed into a PRD or one-pager.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.