pick-issue skillA
pick-issue is agent-read markdown (skill) from rshade/finfocus: Pick the next GitHub issue(s) to work on from the finfocus roadmap backlog and optionally promote them to roadmap/current. Use when the user asks "what should I work on next", "pick an issue", "what's next on the roadmap", "promote an issue to current", or before starting work on an unplanned issue. Ranks open roadmap/next and roadmap/future issues by a documented scoring rubric (effort, unblocks, epic promotion, triggers), respects suppression rules (parked, timebox/watch, unfired trigger-pendi.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Pick Issue Interactive selection of the next issue(s) to work, with optional promotion to `roadmap/current`. This is the standalone picking workflow extracted from the `/roadmap sync` promotion gate — it does not rewrite ROADMAP.md wholesale or sync labels repo-wide. ## Preconditions - `gh` CLI authenticated for `rshade/finfocus`. - Repo root has `ROADMAP.md` and `CONTEXT.md`. If either is missing, skip the file-update steps below and limit yourself to label flips — say so in the summary. - Read `CONTEXT.md` first. Any candidate that would cross a CONTEXT.md boundary must be flagged, not silently promoted. ## Step 1 — Gather candidates ```bash # Phase labels: roadmap/current | roadmap/next | roadmap/future (mutually exclusive) gh issue list --state open --label roadmap/next --limit 100 \ --json number,title,labels,body,milestone gh issue list --state open --label roadmap/future --limit 100 \ --json number,title,labels,body,milestone # Cross-check what is already in flight gh issue list --state open --label roadmap/current --limit 100 --json number,title ``` Excluded from candidacy (never present them): …
Read the whole file at its exact version.
How to install
mdr add rshade/finfocus/pick-issue@git:20260923.40f7ademdr add rshade/finfocus/pick-issue@sha256:b145dd6913228721Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ei4v2bxgznhdca2f)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6438 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
rshade/finfocus · 10 stars · license Apache-2.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ei4v2bxgznhdca2f GET https://markdownregistry.com/api/v1/resolve?ref=rshade/finfocus/pick-issue GET https://markdownregistry.com/api/v1/blob/b145dd6913228721065c6272808038a16e77366fed06df5db639a8e0e2054a4d
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.