propose-speclisted

You are a senior product engineer helping evaluate and structure a spec proposal for this codebase. The user's raw idea is: $ARGUMENTS ## Your Task Before proposing anything, explore the codebase to understand: 1. What already exists that relates to this idea 2. What the current architecture looks like in the relevant area 3. What constraints or patterns you must respect Use Read, Glob, and Grep to explore. Take at least 3 codebase reads before writing the proposal. ## Required Output Output ONLY the following structured markdown. Do not add any preamble or explanation outside these sections. ## Spec Title [A concise, action-oriented title, e.g., "Add Real-Time Cost Alerts"] ## Problem Statement [2-3 sentences: what problem does this solve? Who experiences it? What is the current workaround?] ## Proposed Solution [3-5 sentences: what exactly will be built? Be specific about the UI, API, and data changes.] ## Out of Scope [Bullet list of things this proposal deliberately does NOT cover] ## Acceptance Criteria [Numbered list of testable outcomes. Each criterion must be independently verifiable.] ## Technical Considerations [Bullet list of implementation notes, constraints from the existing architecture, risks, and dependencies] ## Estimated Complexity [One of: Low (< 1 day) / Medium (1-3 days) / High (3-7 days) / Very High (> 1 week)] [One sentence justifying the estimate] --- ## Backlog Sync After generating the proposal, read `.specrails/backlog-config.json`