pick-issue-and-plan

Select a GitHub issue, generate an implementation plan, and commit it.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/dezverev/AnimalAL-v1 --skill pick-issue-and-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pick-issue-and-plan
Source: https://github.com/dezverev/AnimalAL-v1/tree/main/.cursor/skills/pick-issue-and-plan
Command: npx skills add https://github.com/dezverev/AnimalAL-v1 --skill pick-issue-and-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of discovering open GitHub issues, classifying them by priority, and turning a chosen issue into a concrete, executable plan saved under the project's Pending work queue, thereby accelerating structured software planning.

Core Features & Use Cases

  • Issue discovery & classification: Uses the GitHub MCP server (list_issues) or gh CLI fallback to surface open issues, excluding those labeled AIIGNORE or FUTUREWORK, and tagging them as maint or feat.
  • Plan generation & commit: For the selected issue, fetches full details, analyzes the codebase, and writes a detailed implementation plan to .cursor/workplans/Pending/<slug>.md, then commits the plan on the current branch.
  • Issue lifecycle management: Closes the chosen issue with state_reason "not_planned" to reflect that planning has captured the work.
  • Workflow interop: Prefers MCP; gracefully falls back to gh if the MCP server is unavailable.

Quick Start

Tell the agent to pick an issue and plan. It will locate an eligible open issue, generate a detailed plan, commit it to the Pending folder, and mark the issue as not_planned.

Frequently Asked Questions about pick-issue-and-plan

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

FAQPage Schema
How do I automatically generate implementation plans from GitHub issues?

To generate implementation plans from GitHub issues, the skill discovers open issues via GitHub MCP or gh CLI, filters out ignored labels, analyzes the codebase, and writes a plan to .cursor/workplans/Pending. It then commits the plan and closes the issue automatically.

Can I use the GitHub MCP server to triage and prioritize open issues?

Yes, you can use the GitHub MCP server to triage open issues. The skill uses list_issues to discover issues, classifies them as maint or feat, and excludes items labeled AIIGNORE or FUTUREWORK to prioritize actionable work.

What is the best way to turn a GitHub issue into a pending workplan file?

The best way to turn a GitHub issue into a workplan is selecting a prioritized issue, analyzing repository context, and saving a detailed plan file to .cursor/workplans/Pending/<slug>.md. The skill commits this plan to your current branch.

Does this issue planning workflow work if the GitHub MCP server is unavailable?

Yes, the issue planning workflow works if the GitHub MCP server is unavailable. It gracefully falls back to the gh CLI to list, read, and write issues, ensuring plan generation and issue closure proceed without interruption.

Why does the skill close a GitHub issue with the state reason not_planned?

The skill closes a GitHub issue with state_reason not_planned to signal that the work has been captured in a generated implementation plan. This prevents duplicate planning efforts while preserving the issue history in the repository.

How do I exclude specific GitHub issues from automated planning?

To exclude specific GitHub issues from automated planning, apply the AIIGNORE or FUTUREWORK labels to them. The skill filters out any issues carrying these labels during the discovery and triage phase.