issue-plan

Automate GitHub issue deep-dives across research, innovate, and plan phases.

1.1k|68|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/vm0-ai/vm0 --skill issue-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-plan
Source: https://github.com/vm0-ai/vm0/tree/main/.claude/skills/issue-plan
Command: npx skills add https://github.com/vm0-ai/vm0 --skill issue-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the start of work on a GitHub issue by orchestrating a structured deep-dive workflow (research, innovate, plan) with automated task tracking and comments. This helps teams ensure consistent exploration and planning for new issues.

Core Features & Use Cases

  • Todo-driven deep-dive workflow: automatically initializes and updates all phases (fetch issue details, check artifacts, execute research → innovate → plan, post comments, and finalize with a pending label).
  • Automated phase execution: runs research, innovation, and planning in sequence with an auto-continue mode and keeps a live todo list updated.
  • Comment posting and artifact management: posts phase results as issue comments and stores interim artifacts in /tmp/deep-dive folders for traceability.
  • Use Case: When a new GitHub issue is opened, the skill can kick off a structured deep-dive, document findings, propose a plan, and prepare actionable steps for the team.

Quick Start

Start a deep-dive on an issue by providing its ID. For example, begin issue 123 to trigger the automated research, innovation, and planning phases, with results posted as comments and the issue labeled pending when awaiting human review.

Frequently Asked Questions about issue-plan

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

FAQPage Schema
How do I automate GitHub issue planning before starting development?

Automate GitHub issue planning by triggering a structured deep-dive workflow that sequentially executes research, innovate, and plan phases. It fetches issue details, manages interim artifacts, and posts the finalized plan as a comment.

What is a todo-driven deep-dive workflow for GitHub issues?

A todo-driven deep-dive workflow automatically initializes and updates a live todo list across research, innovation, and planning phases. It enforces branch naming conventions and posts phase results as comments for team traceability.

Do I need the GitHub CLI to automate issue tracking and comments?

Yes, you need the GitHub CLI installed and configured with appropriate repository access to automate issue tracking. The workflow uses the CLI to fetch issue details, post phase result comments, and apply the pending label for review.

How does automated issue planning manage interim research artifacts?

Automated issue planning manages interim research artifacts by storing them in /tmp/deep-dive folders during execution. This ensures full traceability of the research, innovate, and plan phases before finalizing the output as a GitHub comment.

Can I automatically label GitHub issues pending human review after planning?

Yes, you can automatically label GitHub issues pending human review after the deep-dive planning completes. The workflow finalizes the research, innovation, and planning sequence by applying a pending label to signal the team.

When should I use an automated deep-dive workflow for GitHub issues?

Use an automated deep-dive workflow for GitHub issues requiring structured exploration and planning across research, innovate, and plan phases. It is ideal for teams needing consistent documentation, proposed plans, and actionable steps.