Pull Task Skill

Queries a GitHub project board or Jira and presents candidates for the user to select as their next task.

Operation

When: User needs to pick the next task from the project board.

Implementation: Load operations/github-backend.md (GitHub) or operations/jira-backend.md (Jira) for detailed steps.

Quick summary: Detects backend (GitHub or Jira) from workspace context, fetches items filtered by status/sprint, ranks candidates, presents for selection, outputs issue reference for /create-workspace.

Backend Detection

The skill detects which backend to use by checking workspace CLAUDE.md:

• GitHub Issue: field present → GitHub backend
• Jira Ticket: field present → Jira backend
• Neither or both → Ask user via AskUserQuestion

Common Patterns

GitHub Backend

Cache sync: project-board-helper sync refreshes the local SQLite cache at ~/Library/Caches/<project>/project-board.db.

Item filtering: sqlite3 queries against the cache DB, filtering by Status and Sprint field values.

Field metadata: project-board-helper field <name> returns field IDs and option IDs.

Item lookup: project-board-helper lookup <owner/repo> <number> resolves issue to project item ID.

Issue reference: Constructed from repo + # + issue_number (e.g., <owner>/<repo>#77).

Jira Backend

Authentication check: acli jira auth status

Issue search: acli jira workitem search --jql "<query>" --json

Default JQL (Scrum): sprint in openSprints() AND status = "To Do" AND project = <KEY>

Default JQL (Kanban): status in ("To Do", "Backlog") AND project = <KEY>

Issue reference: Project key + issue number (e.g., DO-123).

Permissions

GitHub

Jira

Commands