pick-issue-and-plan-claude

Select an open 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-claude
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pick-issue-and-plan-claude
Source: https://github.com/dezverev/AnimalAL-v1/tree/main/.claude/skills/pick-issue-and-plan-claude
Command: npx skills add https://github.com/dezverev/AnimalAL-v1 --skill pick-issue-and-plan-claude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the transformation of open GitHub issues into concrete implementation plans by selecting the most relevant issue, analyzing the repository, and generating a detailed Pending plan that documents steps, required skills, and context for execution.

Core Features & Use Cases

  • Issue discovery and prioritization: Discovers open issues, excludes AIIGNORE/FUTUREWORK, prioritizes maint over feat, and selects a single action item.
  • Plan generation: Analyzes the codebase and issue details to produce a structured implementation plan saved under .claude/workplans/Pending/.
  • Automation of workflow state: Commits the plan on the current branch and marks the issue as not_planned to close it from active tracking.
  • Fallback strategies: Uses GitHub MCP tools when available and gracefully falls back to gh CLI when MCP is unavailable.

Quick Start

Invoke the skill to identify an open maint or feat issue, generate a detailed implementation plan, and place it in .claude/workplans/Pending/<slug>.md.

Frequently Asked Questions about pick-issue-and-plan-claude

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

FAQPage Schema
How do I turn GitHub issues into implementation plans automatically?

This skill selects the next actionable GitHub issue, analyzes your repository scope, and generates a detailed implementation plan saved under .claude/workplans/Pending/ with a slug derived from the issue.

How does the issue prioritization process work for GitHub workflow automation?

Issue prioritization discovers open issues, excludes AIIGNORE and FUTUREWORK tags, prioritizes maint over feat types, and selects a single action item to plan.

Can I use GitHub MCP tools instead of the gh CLI for issue management?

Yes, the skill uses GitHub MCP tools when available and gracefully falls back to the gh CLI when MCP is unavailable to commit plans and mark issues as not_planned.

What happens to a GitHub issue after the implementation plan is generated?

After generating the plan, the skill commits it on the current branch and marks the GitHub issue as not_planned to close it from active tracking.

Do I need any dependencies installed to generate workplans from GitHub issues?

No external dependencies are required, but the skill prefers GitHub MCP tools for automation and falls back to the gh CLI if MCP is unavailable.

What are the limitations of automated GitHub issue planning?

The skill only processes open maint and feat issues, excludes AIIGNORE and FUTUREWORK tagged issues, and generates plans exclusively in .claude/workplans/Pending/ using a slug naming convention.