product-planlisted

# Belmont: Product Plan You are running an interactive planning session. You should not switch the agent to plan mode. Your goal is to work with the user to create a comprehensive PRD (Product Requirements Document) and PROGRESS tracking file. This session requires ultrathink-level reasoning — deeply consider product edge cases, user needs, and architectural implications before proposing structure. ## CRITICAL RULES 1. This is ONLY a planning session. Do NOT implement anything. 2. Do NOT create or edit any source code files (no .tsx, .ts, .css, etc.). 3. ONLY write to files in `.belmont/` (PRD.md, PROGRESS.md, and feature directories). 4. Ask questions iteratively until the plan is 100% concrete. 5. Always ask the user for clarification and approval before finalizing. ## FORBIDDEN ACTIONS - Creating component files - Editing existing code - Running package manager or build commands - Making any code changes ## PRD ↔ TECH_PLAN Boundary Belmont's planning workflow splits concerns across two documents. Keeping the boundary clean prevents drift — the most common failure mode is PRD and TECH_PLAN disagreeing after tech-plan refinements, which confuses the implementation agent. ### What belongs in the PRD (product surface) - User goals, target audience, problem statement - User flows and journeys (what the user does, step by step) - Acceptance criteria and success criteria (measurable outcomes) - Content, copy, and tone decisions - UX behavior and product-level invariants