Working Backwards Coach

Create rigorous customer-first product documentation for product builders. Use when someone wants to evaluate a product idea, write PR/FAQ documents, create working-backwards docs, define product requirements (PRDs), validate product-market fit, or needs help thinking critically about whether to build something. Helps force customer perspective, identify assumptions, and produce concise decision-oriented docs (PR/FAQ, PRDs, narratives, journey maps). Triggers include requests for product strategy, feature proposals, "should we build", PRDs, "product requirements document", product validation,

12 stars 6 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add nwadmark/working-backwards-coach --skill working-backwards-coach
Manual install
git clone --depth 1 https://github.com/nwadmark/working-backwards-coach.git /tmp/working-backwards-coach
mkdir -p ~/.claude/skills
cp -r /tmp/working-backwards-coach/. ~/.claude/skills/working-backwards-coach

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Working Backwards Doc Coach

Transform product ideas into crisp, customer-first documentation that enables evidence-based decisions.

## Core Workflow

When a user presents a product idea, follow this sequence:

### 0. Determine Documentation Scope

Unless the user specifies otherwise, ask which format they need:

**Option 1: Quick 1-Pager (Recommended for initial evaluation)**
- Single page decision document
- Includes: Customer/Problem, Key Benefit, Critical Assumptions, Recommendation (Build/Investigate/Pivot/Kill)
- Best for: Fast decision-making, busy stakeholders, first pass evaluation
- Output: MD only

**Option 2: Product Requirements Document (PRD)**
- Detailed product specification for engineering and design teams
- Includes: Overview, Goals & Non-Goals, User Stories, Requirements (Functional/Non-Functional), Success Metrics, Technical Considerations, Open Questions
- Best for: After decision to build is made, engineering handoff, cross-functional alignment
- Output: Both MD and DOCX

**Option 3: Comprehensive Working-Backwards Documentation**
- Full 2-page product documentation with customer-first approach
- Includes: All sections (PR/FAQ, Journey, Competitive Analysis, Evidence Plan)
- Best for: Detailed planning, team alignment, formal proposals, validating product-market fit
- Output: Both MD and DOCX

**Option 4: Custom**
- User selects specific sections they need
- Mix and match based on their requirements
Read the full skill on GitHub

Details

Skill name
working-backwards-coach
License
MIT
Repo updated
27 October 2026

FAQ

What does the Working Backwards Coach skill do?

Create rigorous customer-first product documentation for product builders. Use when someone wants to evaluate a product idea, write PR/FAQ documents, create working-backwards docs, define product requirements (PRDs), validate product-market fit, or needs help thinking critically about whether to build something. Helps force customer perspective, identify assumptions, and produce concise decision-oriented docs (PR/FAQ, PRDs, narratives, journey maps). Triggers include requests for product strategy, feature proposals, "should we build", PRDs, "product requirements document", product validation,

How do I install the Working Backwards Coach skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add nwadmark/working-backwards-coach --skill working-backwards-coach. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Working Backwards Coach popular?

It lives in nwadmark/working-backwards-coach, which has 12 GitHub stars and 6 forks.

Related skills

Hanxiaoyu Visual Story Comic

13

rolfie-han/hanxiaoyu-visual-story-comic

Turn original, public-domain, or user-authorized stories, scripts, articles, and outlines into coherent multi-page comics with stable characters, scenes, props, page plans, image prompts, optional image generation, and continuity review. Use when the user asks for 漫画、条漫、绘本式故事页、连续分镜图、story comic、webtoon, comic pages, or a narrative image sequence. Do not use for a single unrelated illustration, a pure film storyboard, or unauthorized imitation of protected characters and living artists.

Writing & Content

Create Heartflow

13

BboTTM/heartflow-skill

Create and evolve a HeartFlow skill. Supports archetype-based characters and real-person reconstruction from chats, screenshots, docs, exported social chat logs, and notes. | 创建并进化一个恋爱 skill。

Writing & Content

Human Readable Reports

14

SummerRiversound/human-readable-reports

Use when writing an analysis, report, findings, or status doc for humans to read and share — not a spec an agent executes. Fights AI verbosity/slop and makes deep content easy to read.

Writing & Content

Syntax Style

15

aref-vc/syntax-style-skill

Craft and revise prose at the sentence level using the syntactic techniques in Virginia Tufte's "Artful Sentences: Syntax as Style". Use when the user asks to write, edit, sharpen, or vary prose, fix flat or monotonous writing, improve rhythm and flow, rework AI-sounding sentences, or wants stronger sentence craft in essays, posts, copy, emails, decks, or documentation. Triggers on "make this read better", "vary the sentences", "this is flat/robotic/monotone", "tighten this", "fix the rhythm", "rewrite this paragraph", "sentence-level edit", or "Artful Sentences". Operates on the prose itself,

Writing & Content

Humanizer Formal

14

jiutianxvanyin/humanizer-formal

降低商务与学术文本的 AI 生成感,中英文均适用。Removes AI-writing patterns from business and academic prose, in both Chinese and English. 用于审校已写好的报告、备忘录、论文、摘要、执行摘要,或在起草时预防机器腔。当用户要求「去 AI 味」「让文字更像人写的」「润色成正式书面语」「检查这段像不像 AI 写的」,或提交商务、学术文本请求改写时使用。Use when the user asks to humanize, de-slop, or remove the AI tone from a report, memo, paper, abstract, or executive summary. 不适用于随笔、营销文案、社交媒体、创意写作。Not for essays, marketing copy, social media, or creative writing.

Writing & Content

Save Progress

15

charlie947/save-progress

Capture a whole working session's learnings into durable memory without overwriting what is already there. Use at the END of a session whenever the user says "save progress", "save our progress", "bank what we learned", "capture the learnings", "save this for next time", "lock in our corrections", or otherwise asks to commit a session's decisions, corrections and best practices. Sorts every learning by HOW LONG IT SHOULD LAST (durable rule / one-off override / project state / lesson), guards against a one-time choice becoming a permanent rule, writes additively so nothing is clobbered, and pri

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.