← ClaudeAtlas

preflightlisted

Fill in the product-mode pre-flight checklist for the current work and save it to .product-mode/checklist/. Use when the user types /preflight.
sohaibt/product-mode · ★ 171 · AI & Automation · score 88
Install: claude install-skill sohaibt/product-mode
# Pre-flight checklist Fill in the five pre-flight boxes for the work the user describes. Use the text after the command as the work description. If there is no text, use the current conversation. 1. Check `.product-mode/checklist/` for a checklist on the same topic. If one exists, build on it and tell the user its path. 2. Draft each box from the conversation, the code, and `.product-mode/decisions/`: - **Problem:** Whose pain are we solving, in one sentence? - **Why now:** What changed? (evidence, trigger, cost of waiting) - **Scope:** Smallest change that tests the hypothesis - **Primary metric:** The one number we expect to move - **Reversibility:** One-way or two-way door? 3. Mark each drafted answer *validated* (the user said it or data shows it) or *assumed* (you inferred it). Never invent evidence, data, or a baseline. 4. Show the draft. Ask about empty or assumed boxes in one short batch. Ask only questions whose answers change the work. 5. When the user confirms, save the file as `.product-mode/checklist/<UTC timestamp>-<work-slug>.md`. Use the timestamp format `2026-01-31T09-05-00-000Z` and a lowercase, hyphenated slug. Use this content: ```markdown # Product-Mode Pre-Flight Checklist **Work:** <work description> **Date:** <YYYY-MM-DD> ## Answers - **Problem**: <answer> - **Why now**: <answer> - **Scope**: <answer> - **Primary metric**: <answer> - **Reversibility**: <answer> --- *Generated by product-mode /preflight* ``` 6. Tell the user the