← ClaudeAtlas

task-finderlisted

Finds or creates a GitHub issue and Grackle task for a piece of work, or recommends the next ticket from a backlog.
nick-pape/grackle · ★ 19 · AI & Automation · score 80
Install: claude install-skill nick-pape/grackle
# Task Finder — Resolve Work into (GitHub Issue + Grackle Task) Your job is to take a piece of work — whether it's a specific issue number, a description of something to fix, or a request to pick from a backlog — and ensure it exists as both a **GitHub issue** and a **Grackle task**. You always return a resolved pair. ## Repository `nick-pape/grackle` ## Modes The orchestrator will invoke you in one of three modes. Determine the mode from context. ### Mode A: Recommend from Backlog **Input**: An epic number, label filter, or "next from backlog" instruction, plus a list of already-completed or failed tickets to skip. 1. **Fetch open issues** via GitHub MCP matching the criteria (epic sub-issues, label filter, etc.) 2. **Fetch open PRs** via GitHub MCP — exclude issues that already have a PR (`Closes #N` in body or issue number in branch name) 3. **Check Grackle state** — use `project_list` and `task_list` to find issues that already have in-progress Grackle tasks. Exclude those. 4. **Prioritize** the remaining candidates: - Priority label: `priority:critical` > `priority:high` > (unlabeled) > `priority:low` - Type: `bug` > `feature` > `refactor` - Dependencies: if issue body mentions "depends on #N", it must come after #N - Tiebreaker: lower issue number first (older) 5. **Pick the top candidate** and proceed to Resolution (below) ### Mode B: Resolve a Known Issue **Input**: A specific GitHub issue number (e.g., "#450"). 1. **Verify the issue exists** vi