Product Plan

Step 1: Read the project

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

Starting mid-flow on an existing project: if code exists but .harness/ is absent, treat this as step 2 — /ideate was skipped. Read the codebase and README to reconstruct what idea.md would have said, then proceed.