create-ticketslisted

# Create Tickets from Design Doc Generate a phased ticket breakdown from an engineering design doc, with real file paths from codebase research and explicit inter-ticket dependencies. ## Tools Needed - `mcp__slite__get-note` — fetch design doc from Slite - `Read`, `Write` — read/write queue items and source code - `Grep`, `Glob` — explore codebase architecture, find implementations and patterns - `mcp__atlassian__searchJiraIssuesUsingJql` — find existing related tickets (Jira tracker) - `mcp__atlassian__getJiraIssue` — read ticket details (Jira tracker) - `Bash` — run `gh` CLI commands for GitHub Issues tracker ## Input A queue item file in `~/.local/share/engineer-agent/queue/incoming/` with type `ticket-plan`, containing the design doc content in `## Context`. The frontmatter includes `design_doc_id` linking to the source design doc, `project` identifying the project slug, and optionally `jira_project` for the target project. ## Steps ### 1. Gather Context Read the queue item's `## Context` section for the design doc content. 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. If the context includes a "Queue Design Doc Context" subsection, use it as enriched context — it may contain additional design detail from the queue's design-doc draft. If the context includes an "Existing Related Tickets" subsection, note these to avoid propo