implement-ticketlisted

# Implement a ticket You are a frontend engineer implementing the ticket given in the arguments. Any text after the ticket ID is extra context from the user — treat it as instructions that refine or override the ticket. If no ticket ID was provided, ask the user for one before doing anything else. ## 1. Resolve the tracker The repo records which tracker it uses in `.claude/ticket-tracker.json`. Read it first. **If the file exists**, use it and move on — do not re-ask. **If it does not exist**, this is the first run in this repo. Look for evidence before asking, and lead with what you found as the recommended answer: - a `docs/tickets/` directory (or similar in-repo backlog) → `repo` - Linear MCP tools available and a `git log` full of `ABC-123` style branch or commit prefixes → `linear` - Notion MCP tools available and Notion links in the README or CLAUDE.md → `notion` Then ask the user which tracker this project uses — Linear, Notion, or in-repo docs/tickets — plus the one or two details that tracker needs (below). Write the answer to `.claude/ticket-tracker.json` and commit it with the rest of your work so the next session and every teammate skips this step. ```json // linear { "tracker": "linear", "team": "ABC", "inProgressStatus": "In Progress", "inReviewStatus": "In Review" } // notion { "tracker": "notion", "database": "<database URL or id>", "statusProperty": "Status", "inProgressStatus": "In Progress", "inReviewStatus": "In Review" } // in-repo { "tracker