issue-actionlisted

<!-- Internal maintenance skill — edit this file directly --> # /issue-action: Implement from Approved Plan Continue working on a gstack-game GitHub issue by implementing the approved plan from `/issue-plan`. ## Arguments Parse `$ARGUMENTS` to get the issue ID. If provided, use it. Otherwise, look for the issue ID from conversation context (from prior `/issue-plan` invocation). If no issue ID found, ask: "Which issue are you implementing? Provide the issue number." ## Task Tracking (CRITICAL) **You MUST use TodoWrite to track progress.** Create this todo list at START: 1. Retrieve context and artifacts 2. Fetch latest issue updates 3. Remove planned label 4. Analyze feedback 5. Execute implementation 6. Run build and tests 7. Create PR 8. Post completion to issue **Update after completing each step.** --- ## Step 1: Retrieve Context and Artifacts Locate deep-dive artifacts: ```bash ls .tmp/deep-dive/issue-{id}/ 2>/dev/null ``` Verify existence of: - `research.md` — Research phase output - `innovate.md` — Innovation phase output - `plan.md` — Implementation plan (REQUIRED) If `plan.md` doesn't exist, **STOP**: "No plan found. Run `/issue-plan {id}` first." Read artifacts in order: `plan.md` → `research.md` → `innovate.md` **Update todo:** Mark completed. --- ## Step 2: Fetch Latest Issue Updates ```bash gh issue view {issue-id} --json title,body,comments,labels ``` Check for new comments since plan was posted. **Update todo:** Mark completed. --- ## Ste