Menu
(Codex) Build a ranked backlog from open issues, or execute a ranked subset of issues by delegating to the Orchestrator in sequence.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Template starter skill for documenting a reusable development workflow. Use this as a base when creating project-specific skills.
(Gemini) Workflow to coordinate multi-step delivery through implementation, review, triage, and commit decisions.
(Gemini) Main-agent workflow for multi-step delivery — delegates discovery, implementation, and review to specialized subagents.
(Gemini) Reviews dashboard and data-heavy admin pages for scanability, KPI hierarchy, chart-task fit, and actionability; produces prioritized UI improvements and implementation tasks.
(Gemini) Frontend implementation guidance for this app. Use before coding visible UI, including forms, dashboards, tables, filters, overlays, navigation, layout, microcopy, accessibility, and i18n.
(Gemini) Use the shared issue workflow runner to generate a ranked backlog or execute a ranked issue subset with an explicit target.
Based on SOC occupation classification
| name | agent-issues-workflow |
| description | (Codex) Build a ranked backlog from open issues, or execute a ranked subset of issues by delegating to the Orchestrator in sequence. |
Use this skill when working with project issues — either building a ranked backlog or executing ranked issues with an explicit target.
If you need a tool that is not available (e.g. gh CLI not installed or not authenticated), stop and tell the user what tool you need, why, and what they should do to provide access. Do not invent ad-hoc alternatives.
Fetch all open issues, score and rank them, and return a prioritized list with a short rationale for each ranking decision. Do not execute any work.
Take a ranked issue list (from a prior backlog run or provided by the user) and execute each issue in order by delegating to the Orchestrator skill. Require an explicit target and explicit issue scope before starting.
all open (default).backlog (default) or execute.Score each issue on:
Present the ranked list as a table: issue reference, title, score rationale, estimated effort, suggested priority.
Backlog mode: one row per issue with: reference, title, rank, score rationale, estimated effort.
Execute mode: after each issue closes, one row with: reference, terminal status, resolution summary, any issues recorded during the run.