skills.rest
AppsVortex
AppsVortexOFFICIAL
Explore all skills by this author →
GitHub

arn-code-pick-issue

Filter GitHub, Jira, or local backlog issues and route the selected one to Arness planning workflows.

31|3|Updated Apr 3, 2026
Search Tags:#workflow#planning#GitHub#backlog#Jira#issue-tracking#spec-generation
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-code-pick-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arn-code-pick-issue
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-code/skills/arn-code-pick-issue
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-code-pick-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineering teams filter, evaluate, and select the most actionable issue from remote trackers (GitHub or Jira) or a local greenfield backlog, then route it to the appropriate Arness pipeline skill for implementation.

Core Features & Use Cases

  • Filter issues by type, priority, and state across GitHub, Jira, or local backlog.
  • Validate and confirm issue readiness, fetch full issue context, and present clear next steps.
  • Hand off to the corresponding spec or planning workflows, with support for local feature files and decomposition into sub-features when applicable.
  • Optional local backlog integration to surface unblocked features before remote browsing.

Quick Start

Start the skill to fetch issues, apply your filters, and select an item to route to the appropriate spec pipeline.

Frequently Asked Questions about arn-code-pick-issue

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

FAQPage Schema
How do I pick the most actionable issue from a GitHub or Jira backlog?▼

Pick the most actionable issue by filtering your GitHub or Jira backlog by type, priority, and state, then fetching full issue context to validate readiness before routing it to your development pipeline.

What is the best way to route a selected issue to a spec generation workflow?▼

Route a selected issue to spec generation by fetching its full context, confirming readiness, and handing it off to the corresponding planning workflow with optional local backlog support for feature decomposition.

Can I filter GitHub and Jira issues by priority and state before planning?▼

Yes, you can filter GitHub and Jira issues by priority and state before planning. The skill evaluates remote trackers and local backlogs to surface ready items, validate their context, and present clear next steps for implementation.

Does issue tracking workflow support local backlogs alongside remote trackers?▼

Yes, issue tracking workflow supports local backlogs alongside remote trackers. You can surface unblocked local features first, validate their readiness, and route them to appropriate spec or planning workflows with full contextual propagation.

Why does my issue routing workflow need full issue context before spec generation?▼

Your issue routing workflow needs full issue context before spec generation to validate readiness and ensure complete contextual propagation. Fetching full details prevents incomplete feature decomposition and misdirected planning downstream.

Related Skills

Explore More Software Engineering Skills→
JuanMS20JuanMS20

github-auth

Configure GitHub authentication for Hermes Agent using git, gh CLI, or SSH credentials.

Community
Intermediate
DocaariDocaari
1

pm-spec

Transform high-level feature descriptions into structured specs with acceptance criteria.

Community
Advanced
markus41markus41
18

jira:pr

Create GitHub pull requests linked to Jira issues and transition them to In Review.

Community
Intermediate
atlassianatlassian
949

triage-issue

Triages bug reports by searching Jira for duplicates and generating structured issues.

Official
Intermediate