Verified:GitHub

plan-issue

Generate and post an implementation plan for a GitHub issue with a plan-pending label.

Updated Apr 10, 2026

Search Tags:#automation #github-issues #implementation-planning #CI-orchestration #label-driven-workflow #trusted-author-gating

Ready to run

npx skills add https://github.com/rjskene/pipeline --skill plan-issue-rjskene

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-issue
Source: https://github.com/rjskene/pipeline/tree/main/skills/plan-issue
Command: npx skills add https://github.com/rjskene/pipeline --skill plan-issue-rjskene

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill converts a GitHub issue into a structured, ready-to-execute implementation plan while enforcing trust boundaries and preventing untrusted automation.

Core Features & Use Cases

Trusted-only planning gate: Checks the issue opener’s authorAssociation and refuses auto-planning for untrusted openers, surfacing the issue for human triage instead.
Path-aware planning: Chooses a planning mode (A/B/C/D) based on labels (or a cached recommended_path from trusted classification feedback).
End-to-end plan posting: Drafts the canonical “Implementation Plan” comment, publishes it via the shared helper, and applies the plan-pending label.
Revision-safe updates: When trusted feedback exists on an earlier plan, rewrites the plan with a required “Changes from previous plan” section.
Label-aware browser predicates: For needs-browser issues, requires machine-checkable predicates the browser-evaluation sub-skill can run.

Quick Start

Tell the AI to run /pipeline:plan-issue <issue_number> to produce and post an implementation plan comment for that issue and mark it as plan-pending.

Frequently Asked Questions about plan-issue

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

FAQPage Schema

How do I automatically generate an implementation plan from a GitHub issue?▼

To generate an implementation plan from a GitHub issue, trigger the plan-issue pipeline command with the issue number. It drafts a canonical plan comment, publishes it, and applies a plan-pending label to the issue.

Can I restrict automated issue planning to trusted contributors only?▼

Yes, automated issue planning can be restricted to trusted contributors using a trusted-opener gate. It checks the author association and refuses auto-planning for untrusted openers, surfacing them for human triage.

How does label-driven workflow automation choose a planning path for GitHub issues?▼

Label-driven workflow automation selects a planning path by reading specific GitHub issue labels. It can also use a cached recommended path from prior trusted classification feedback to determine the correct planning mode.

How do I update an existing implementation plan comment based on new feedback?▼

To update an existing implementation plan, the workflow detects trusted feedback on an earlier plan and rewrites it. The revised comment includes a required Changes from previous plan section to ensure revision-safe updates.

How are GitHub issues requiring browser testing handled during implementation planning?▼

GitHub issues requiring browser testing enforce label-aware browser predicates during implementation planning. This requires machine-checkable predicates that a browser-evaluation sub-skill can execute to validate the conditions.

What happens to the terminal state of a GitHub issue after posting an implementation plan?▼

After posting an implementation plan, the workflow handles the terminal state by applying a plan-pending label to the GitHub issue. This communicates that the issue is awaiting execution of the published plan.