菜单
Pick the next actionable work item from GitHub Issues. Filters open issues labeled agent-ready (spec settled, not blocked), surfaces umbrella/blocked context. Use when starting fresh work or asking 'what should I do next?'
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Close the loop on a rosetta PR's bot review threads (CodeRabbit + Copilot) before claiming it's mergeable. Green status checks and a clean reviewDecision do NOT mean mergeable here — main requires all conversation threads resolved, and that's a separate gate. Use when a PR is Ready for Review and you're about to say it's done, when `gh pr merge` is blocked despite green checks, or when the user asks to address/close review comments.
Promote an Inbox bullet from BACKLOG.md to either a GitHub issue (work commitment) or a briefing (briefings/B-NNNN-*.md, research/decision support). Asks which based on whether the work is committed or still needs thinking. Removes the original bullet.
Verify a work item is actually done by running the V-* validation rows its issue cites. Maps V-* IDs to the CI step / test command via VALIDATION.md, runs them, reports pass/fail per row.
Re-extract the legacy Confluence RouterOS documentation export into SQLite. Use for rebuilding the current DB pipeline, not for the manual.mikrotik.com Docusaurus migration.
| name | pick-next-task |
| description | Pick the next actionable work item from GitHub Issues. Filters open issues labeled agent-ready (spec settled, not blocked), surfaces umbrella/blocked context. Use when starting fresh work or asking 'what should I do next?' |
| argument-hint | Optional: a label or keyword to filter (e.g. extraction, mcp) |
The agent's what now? verb. Reads the GitHub Issues queue and returns the next pickable
issue with enough context to start work. (Named for the retired tasks/ file queue — the
verb survives, the backend is now issues; see tasks/README.md.)
An issue is pickable when:
agent-ready — acceptance criteria are settled.blocked and its body names no unresolved "blocked on" issue.umbrella — umbrellas track themes; work happens in child issues.List candidates.
gh issue list --state open --label agent-ready --json number,title,labels,updatedAt
If a filter argument was supplied, match it against titles and labels.
If none are agent-ready, widen with
gh issue list --state open --json number,title,labels,body (the body field is what
holds "blocked on" references and umbrella checklists) and report what exists instead:
discussion-stage issues (unlabeled — could be settled into readiness), blocked issues
(say what each waits on), and umbrella issues (their child checklists show what could
be spawned next). Also point at BACKLOG.md Inbox and open briefings/.
Surface the top pick. gh issue view <n> --comments, then present: number, title,
acceptance criteria, V-* validation rows, and linked briefings or archived
tasks/done/T-*.md files — some issues keep their full spec in the archived task file
(e.g. #26 → T-0038), so read those too.
Remind the close discipline. The eventual PR must say Closes #<n> in its body;
partial landings spawn follow-up issues before merge (issue-pr-linking.instructions.md).
promote-idea.verify-task.