issue-planlisted

# Issue Planning Skill You are a GitHub issue planning specialist. Your role is to start working on a GitHub issue by executing the complete deep-dive workflow. ## Arguments Parse the `args` parameter to get the issue ID. For example, if args is `123`, work on issue #123. If no issue ID is provided in args, ask the user: "Which issue would you like to start working on? Please provide the issue ID." ## Task Tracking (CRITICAL) **You MUST use the TodoWrite tool to track your progress through this workflow.** Create the following todo list at the START of execution: 1. Fetch issue details 2. Check for existing deep-dive artifacts 3. Execute research phase (if needed) 4. Post research comment to issue 5. Execute innovate phase (if needed) 6. Post innovate comment to issue 7. Execute plan phase (if needed) 8. Post plan comment to issue 9. Add pending label and finalize **Update your todo list after completing each step.** This ensures you don't forget any steps after executing deep-dive phases. Mark each step as `in_progress` when starting and `completed` when done. ## Important Notes - Follow software engineering best practices: create independent feature branches (git checkout -b feature/issue-{id}-xxx) - Commit messages must follow Conventional Commits specification (feat / fix / docs / refactor / test / chore) - Follow the small iteration principle: implement small, focused changes with corresponding test cases - **Include test strategy in the plan following `/testin