find-work

Query GitHub Issues and return prioritized eligible tasks ordered by AGENTS.md rules.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ourchitecture/idp --skill find-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-work
Source: https://github.com/ourchitecture/idp/tree/main/.agents/skills/find-work
Command: npx skills add https://github.com/ourchitecture/idp --skill find-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discover the next available issue to work on by querying GitHub Issues, respecting team authorization, priority ordering, and assignment rules from AGENTS.md. Use this skill when you need to discover what to work on next.

Core Features & Use Cases

  • Query Open Issues: Use MCP list_issues to fetch open issues for the repository with state open and label "ready"; if domain is provided, apply domain label filter; fallback to gh CLI if MCP is unavailable.
  • Filter Issues: Exclude issues with in-progress or blocked labels and filter by assignee idle time; check for agent-eligible label; issues without this label are available for humans but noted.
  • Sort by Priority: Rank by who created or assigned by admin/maintain, plus priority labels p0/p1/p2/p3 and oldest creation date as tiebreaker.
  • Format Results: Return up to max_results with number, title, priority, domain labels, agent eligibility, current assignee, age, and recommended worktree steps.

Quick Start

Run the skill to fetch the next eligible GitHub issue to work on for the current repository, optionally filtering by domain.

Frequently Asked Questions about find-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the highest priority GitHub issue to work on next?

Finding the next GitHub issue to work on involves querying open issues, filtering out in-progress or blocked labels, and ranking eligible items by AGENTS.md priority rules including p0-p3 labels and admin assignment to recommend the top task.

How does issue triage automation handle authorization and assignment rules?

Issue triage automation handles authorization by checking for agent-eligible labels and filtering by assignee idle time, excluding issues without proper authorization from automated discovery while still noting them as available for human contributors.

Can I filter GitHub issues by domain when searching for my next task?

Yes, you can filter GitHub issues by domain when searching for your next task by providing a domain parameter, which applies a domain label filter to the open issues query to narrow results to your specific area of expertise.

What's the best way to automate discovery of ready GitHub issues across repositories?

The best way to automate discovery of ready GitHub issues is to use MCP list_issues with state open and label "ready", falling back to gh CLI if MCP is unavailable, then apply priority ordering and readiness filters to return structured eligible results.

Does this issue finder work without the MCP list_issues tool?

Yes, this issue finder works without the MCP list_issues tool by falling back to the gh CLI to fetch open issues, ensuring automated task discovery remains functional even when MCP is unavailable in your environment.

Why are some open issues excluded from my recommended work list?

Some open issues are excluded from your recommended work list because they carry in-progress or blocked labels, lack the agent-eligible label required for automated assignment, or have assignees who have not exceeded the idle time threshold.