product-playbook

Use when implementation work starts on a feature or bug fix: writing or modifying source code, adding tests, or closing out a branch. Covers TDD-first, scope integrity, secret and security hygiene, dual post-implementation review (code reviewer plus spec reviewer), and finish-branch closure. Triggers on "implement", "start coding", "build the feature", "write the code", "fix the bug", "finish the branch", "wrap up the branch", and the same intent in any language ("開始實作", "開發這個功能", "收尾", "実装して").

Use when the user wants the plan rendered as an interactive HTML report or exported to PDF/DOCX/PPTX. Triggers on 'HTML report', 'export to PDF', 'export document', 'downloadable report', 'PDF/DOCX/PPTX', and the same intent in any language.

Use when you need to understand the job a user hires the product to do, before designing or evaluating a solution. Triggers on "jobs to be done", "JTBD", "what job", "user motivation", "why would they use this", "customer needs", and the same intent in any language.

Use when the user needs to decide what makes the first version and what to explicitly not build. Triggers on 'MVP', 'scope', 'not doing list', 'must have vs later', 'user stories', 'parallel prototypes', and the same intent in any language.

Use when the user wants to connect a desired outcome to opportunities and candidate solutions in a structured tree. Triggers on "opportunity solution tree", "OST", "map opportunities", "outcome to solutions", "Teresa Torres", and the same intent in any language.

Use when the user needs to understand who the users are and how they move through an experience. Triggers on "persona", "target user", "buyer vs user", "user journey", "journey map", "touchpoints", and the same intent in any language.

Use when the user is assessing product-market fit or planning go-to-market and pricing. Triggers on 'PMF', 'product market fit', 'go to market', 'GTM', 'acquisition channels', 'pricing', 'business model', and the same intent in any language.

Use when the user needs to position a product against the alternatives customers actually consider. Triggers on "positioning", "competitive alternatives", "differentiation", "April Dunford", "market category", and the same intent in any language.

Use when the user wants to define a product by writing its launch press release and FAQ before building. Triggers on 'PR-FAQ', 'press release', 'working backwards', 'Amazon PR FAQ', 'write the launch announcement', and the same intent in any language.

Use when the user needs an engineer-ready PRD or a development handoff package (CLAUDE.md, TASKS, TICKETS, ARCHITECTURE, setup). Triggers on 'PRD', 'product requirements doc', 'handoff to engineering', 'dev handoff', 'TASKS.md', 'TICKETS', 'architecture doc', and the same intent in any language.

Use when the user needs to consolidate planning into a final spec with a risk register and blind-spot review. Triggers on "spec summary", "final spec", "risk register", "gaps and blind spots", "validation plan", "wrap up the plan", and the same intent in any language.

Use immediately after the user writes or revises a strategy artifact (strategy kernel, DHM, strategy blocks, empowered-team charter) to stress-test it before it propagates. Triggers on "critique this strategy", "is this strategy any good", "poke holes", "red team the strategy", and the same intent in any language.

Use when the user is setting or pressure-testing product strategy, direction, or the case for an opportunity, before committing resources. Triggers on "product strategy", "is this opportunity worth it", "strategy kernel", "DHM", "diagnosis", "guiding policy", "OKR", "empowered team", and the same intent in any language.

Use when the user needs to define how success is measured: a North Star, supporting signals, and the activation moment. Triggers on "North Star metric", "success metrics", "signals", "aha moment", "activation", "Sean Ellis", and the same intent in any language.

MUST use whenever the user is working through a product or feature: planning, scoping, validating, prioritizing, or deciding whether to build it. This includes the open-ended case of exploring whether a raw idea is worth pursuing, who it serves, and what job it does. Triggers on "is this worth building", "should we build", "plan a feature", "add a feature", "product strategy", "MVP", "PMF", "North Star", "PR-FAQ", "positioning", "go/no-go", and the same intent in any language ("規劃新功能", "值不值得做", "新機能を企画").

Use when you have several solution options or features and need to decide what to do first, before scoping an MVP. Triggers on "prioritize", "RICE", "GEM", "impact vs effort", "which should we build first", "rank these", and the same intent in any language.

Use when the user needs to sharpen a vague problem into pain points, reframed questions, and ranked opportunities before designing solutions. Triggers on "frame the problem", "pain points", "how might we", "HMW", "opportunity assessment", "what problem", and the same intent in any language.

Use when you need to surface how a product, feature, or plan could fail before committing to it, especially before a go/no-go decision. Triggers on "pre-mortem", "what could go wrong", "failure modes", "risks", "how might this fail", and the same intent in any language.