extract-product-contextlisted

# Extract product context **A product defines itself in its repo. Everything else describes it.** This skill exists because of a specific, repeatable mistake. On 2026-08-31 the first `context/` written for an app claimed the product ended at birth. No source said that — it was inferred from the vocabulary of the store listing and labelled `[verified]`. The repo held a `ROADMAP.md` with a phase named *Post-Birth Retention*, install and conversion figures, and a written boundary against a sibling product. None of it was read, because the two sources that *talk about* a product — the daily notes and the store copy — are the two that come to mind, and nothing said to look further. So the rule this skill enforces is an ordering, not an effort level. ## Run this first ```bash ~/second-brain-workflow/scripts/context-sources.py --repo "$PWD" ``` Read-only, opens nothing. It lists where the repo states itself, in four tiers of authority, and **names the tiers that are empty** — which is the half that matters, because an empty tier means the answer is not in this repo and must be asked for rather than derived from a tier that happens to be full. ## The four tiers, and why the order is the point | Tier | Holds | Authority | |---|---|---| | 1 · product docs | `ROADMAP.md`, `KNOWLEDGE_BASE.md`, `PRODUCT.md`, `docs/features/**` | **Highest.** Written to state intent — what the product is *for*, where it stops, what it refuses to be | | 2 · store metadata | `store/listings/**`, `met