issue-planner

Generate multi-agent implementation plans for GitHub Issues with ADR and testing artifacts.

Updated Feb 27, 2025
One-click install
npx skills add https://github.com/tuanemuy/dotfiles --skill issue-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-planner
Source: https://github.com/tuanemuy/dotfiles/tree/main/config/claude/skills/issue-planner
Command: npx skills add https://github.com/tuanemuy/dotfiles --skill issue-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issue planning for GitHub issues is automated by running three independent agents to generate a robust, integrated implementation plan and save it to .issue/{Issue番号}/plan.md, with ADR and testing artifacts as needed.

Core Features & Use Cases

  • Parallel three-agent planning to generate comprehensive implementation plans
  • Integrated reviews, ADR logging, and testing plan scaffolding
  • Output to .issue/{Issue番号}/plan.md and related artifacts for traceability

Quick Start

Trigger the Issue Planner against a GitHub Issue to generate a complete plan.

Frequently Asked Questions about issue-planner

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

FAQPage Schema
How do I automate GitHub issue planning for complex tasks?

Automated GitHub issue planning generates structured implementation plans by running parallel agents to handle cross-cutting design decisions. It outputs standardized plan.md, adr.md, and testing.md artifacts directly into the .issue/{Issue番号}/ directory for full traceability.

What is multi-agent issue planning and when do I need it?

Multi-agent issue planning runs three independent agents to generate a robust, integrated implementation plan. It is needed for complex GitHub issues requiring cross-cutting design decisions, Architecture Decision Record (ADR) logging, and formal reviews.

How do I generate an ADR and testing plan from a GitHub issue?

Generate an ADR and testing plan by triggering an automated issue planner against a GitHub issue. It scaffolds the formal review workflow and logs architecture decisions directly into .issue/{Issue番号}/adr.md and testing.md artifacts.

Does multi-agent issue planning work for simple GitHub issues?

Multi-agent issue planning targets complex issues requiring cross-cutting design decisions and integrated reviews. For simple issues without the need for ADR logging or standardized plan templates, this multi-agent approach may be unnecessary overhead.

Can I use the issue planner without a formal review workflow?

The issue planner enforces a formal review workflow alongside standardized plan templates and parallel agent execution. It is designed to produce integrated implementation plans where formal reviews are a required component of the process.

What is the issue-planner Skill for GitHub?

The issue-planner Skill automates structured multi-agent planning for GitHub issues. It coordinates three independent agents to generate comprehensive implementation plans, ADR logs, and testing scaffolding for complex development tasks.