working-backwards-coach

Generate Working-Backwards documentation with PR/FAQ, journey, and evidence plans.

10|6|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/nwadmark/working-backwards-coach --skill working-backwards-coach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: working-backwards-coach
Source: https://github.com/nwadmark/working-backwards-coach/tree/main
Command: npx skills add https://github.com/nwadmark/working-backwards-coach --skill working-backwards-coach

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Transforms vague product ideas into rigorous, customer-first documentation that supports evidence-based decision making across teams.

Core Features & Use Cases

  • Generate Working-Backwards documents (PR/FAQ, PRD, journey narratives, and evidence plans) from a product idea.
  • Coach users to surface customer perspectives, label assumptions, and force specificity before committing to a solution.
  • Provide templates and structured outputs (MD and DOCX) guided by references/document-templates.md and evaluation rubrics.

Quick Start

Ask Claude to create a Working Backwards document for your product idea.

Frequently Asked Questions about working-backwards-coach

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

FAQPage Schema
How do I write a Working Backwards document from a product idea?

A Working Backwards document transforms product ideas into customer-first narratives, PR/FAQs, and evidence plans that surface assumptions and force specificity before committing to a solution. It ensures cross-functional alignment through rigorous, evidence-based documentation.

What is the best way to create a PR/FAQ for product documentation?

Creating a PR/FAQ is done by applying the Working Backwards method to generate customer-first documentation, including press releases and FAQs, from a product idea. This approach forces specificity and surfaces customer perspectives before solution commitment.

Can I generate both a 1-page brief and a full PRD from the same product idea?

Yes, the skill tailors Working Backwards outputs to multiple formats including 1-page briefs, PRDs, or full-comprehensive documents based on your specific needs. It generates appropriate documentation whether you need a quick brief or a full PRD with milestones, risks, and evaluation criteria.

How does evidence-based product documentation help with cross-functional handoffs?

Evidence-based product documentation supports cross-functional handoffs by generating structured outputs with milestones, risks, assumptions, and evaluation criteria. This ensures teams share a rigorous, customer-first understanding of the product idea before solution commitment.

When do I need a Working Backwards document for my product?

You need a Working Backwards document when a product idea requires decision-making, strategic alignment, and cross-functional handoffs. It transforms vague concepts into rigorous, customer-first documentation that surfaces assumptions and forces specificity before solution commitment.

What limitations exist when generating Working Backwards PRDs from vague ideas?

When generating Working Backwards PRDs from vague ideas, the limitation is that the skill requires you to actively surface customer perspectives and label assumptions. The quality of the evidence-based documentation depends on engaging with the coaching process to force specificity before solution commitment.