akka-issueslisted

## User Input You **MUST** consider the user input before proceeding (if not empty). ## Outline 1. **Locate the feature**: Call the `akka_sdd_list_specs` MCP tool to find features. Verify that `tasks.md` exists for the target feature (`has_tasks` must be true). If `tasks.md` is missing, instruct the user to run `/akka:tasks` first. Read the `tasks.md` content from FEATURE_DIR. 2. **Build the task-ID set**: Scan `tasks.md` for every task line — each starts with `- [ ]` followed by a task ID matching `T` and three digits (e.g. `T001`). Collect the set of task IDs you are about to process. 3. **Determine the GitHub repository from the git remote**: ```bash git config --get remote.origin.url ``` > [!CAUTION] > ONLY PROCEED TO THE NEXT STEPS IF THE REMOTE IS A GITHUB URL 4. **Fetch existing issues for deduplication**: Before creating anything, use the GitHub MCP server's `list_issues` tool to find issues that already cover the task IDs from step 2. - Do **not** pass a `state` value — omitting it returns both open and closed issues. - Request `perPage: 100` to minimize calls. - The tool uses cursor-based pagination: request further pages with the `after` parameter using the `endCursor` from the previous response. - For each issue title, match against the pattern `\bT\d{3}\b` (word boundaries so `ST001` and `T0010` do not false-match). This recognizes titles written as `T001 ...`, `T001: ...`, or `[T001] ...`. When it matches one of your task IDs,