auto-propose-backlog-specslisted

Analyze the project from a **product perspective** to generate new feature ideas. Syncs results to GitHub Issues labeled `product-driven-backlog`. Use `/specrails:get-backlog-specs` to view current ideas. **Input:** $ARGUMENTS (optional: comma-separated areas to focus on. If empty, analyze all areas.) **IMPORTANT: This command only creates GitHub Issues.** You may read files and search code to understand current capabilities, but you must NEVER write application code. --- ## Areas Read `.specrails/config.yaml` or CLAUDE.md to identify project areas/modules. If not defined, use high-level categories inferred from the codebase structure (e.g., Frontend, Backend, API, Data, Infrastructure, Developer Experience). --- ## Execution Launch a **single** explorer subagent (`subagent_type: Explore`, `run_in_background: true`) for product discovery. The Explore agent receives this prompt: > You are a product strategist analyzing the this project (read name from CLAUDE.md, package.json, or directory name) to generate new feature ideas using the **Value Proposition Canvas** framework. > > **Your goal:** For each area, propose 2-4 new features that would significantly improve the user experience. Every feature MUST be evaluated against the project's personas. > > **Areas to analyze:** {all areas or filtered by user input} > > ### Step 0: Read Personas > > **Before anything else**, read all persona files: > Read all persona files from `.specrails/personas/*.md` and `.claude/agents