refine-speclisted

# Refine a Feature Spec Analyze a PM's feature spec from Slite and produce structured clarifying questions with rationale. ## Tools Needed - `mcp__slite__get-note` — fetch spec content from Slite - `Read`, `Write` — read/write queue items and source code - `Grep`, `Glob` — search codebase for referenced code and find relevant implementations - `mcp__atlassian__searchJiraIssuesUsingJql` — find related/overlapping tickets - `mcp__atlassian__getJiraIssue` — read related ticket details ## Input A queue item file in `~/.local/share/engineer-agent/queue/incoming/` with type `spec-refinement`, containing the spec content in `## Context`. ## Steps ### 1. Read the Spec Read the queue item to get the full spec content from the `## Context` section. Extract the `project` field from frontmatter. Read `~/.local/share/engineer-agent/engineer.yaml` to find the project config at `projects.<project>` for codebase path and Jira settings. ### 2. Analyze Across Five Dimensions **Scope Clarity** - Are boundaries well-defined? - Are success criteria measurable? - Is it clear what's in and out of scope? **Feasibility** - Can this be built with current systems and architecture? - Are there technical constraints that make parts infeasible? **Missing Details** - Are edge cases addressed? - Is error handling specified? - Are data models described? - Are API contracts defined? **Ambiguities** - Are there statements with multiple valid interpretations? - Are there hidden assumptions? - Are