product-planlisted

# Product Plan ## Step 1: Read the project **Starting mid-flow on an existing project**: if code exists but `.harness/` is absent or empty, treat this as step 2 in the workflow — `/ideate` was skipped. Read the codebase and README to reconstruct what `idea.md` would have said, then proceed with the interview. Before asking anything, gather all available context: **Ideation output** — read `.harness/product/idea.md` if it exists: - Extract: concept, problem, market landscape, competitor list, viability verdict - These questions are already answered — do not re-ask them in the interview **Existing product docs** — read `.harness/product/` for prior decisions to update rather than re-litigate **Codebase** — if code already exists: - Read README.md for stated goals and audience - Scan the feature surface: routes, screens, commands, or API endpoints - Check the roadmap or issue tracker if present (`gh issue list`) - Note what's implemented, what's stubbed, and what's conspicuously absent Synthesize into a one-paragraph internal picture: what it does, who it seems built for, where it's headed. Do not share this — use it to skip questions already answered and form sharper hypotheses for the ones you do ask. ## Step 2: Interview Interview the user relentlessly — one question at a time. For every question, state a concrete recommendation or hypothesis first. Never ask a bare question. Lead with your position — "My read is X. Do you agree?" — so the user reacts to a specific c