gh-issue-kickoff

Translate live GitHub issue data into an execution-ready implementation plan.

3|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/beeman/skills --skill gh-issue-kickoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-issue-kickoff
Source: https://github.com/beeman/skills/tree/main/gh-issue-kickoff
Command: npx skills add https://github.com/beeman/skills --skill gh-issue-kickoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kick off work on a GitHub issue from live GitHub data and current repo context to create an executable, guard-railed plan without waiting for a full review cycle.

Core Features & Use Cases

  • Translate live issue data (title, body, comments, labels) and repository context into an actionable kickoff plan.
  • Enforce readiness criteria and escalation rules to keep planning scoped and safe.
  • Produce a concise, execution-ready plan that starts work immediately while enabling stakeholder alignment.

Quick Start

Provide the first execution-ready implementation plan based on the live issue data.

Frequently Asked Questions about gh-issue-kickoff

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

FAQPage Schema
How do I create an execution-ready plan from a GitHub issue?

Translate GitHub issue data into an execution-ready plan by reading live issue titles, comments, and labels with nearby repository code to produce a minimal, safe kickoff plan and next steps.

What is the best way to start implementation work on a GitHub issue without waiting for a full review?

Kick off issue work without a full review by translating live GitHub issue data and repository context into a guard-railed, execution-ready plan that enables immediate action while maintaining stakeholder alignment.

Can I generate an implementation plan directly from live GitHub issue data?

Yes, generate an implementation plan from live GitHub issue data by applying readiness criteria and escalation rules to issue titles, bodies, comments, and labels to produce scoped, safe execution plans.

Does the kickoff plan include follow-up actions for stakeholders?

Yes, the kickoff plan includes required updates and stakeholder follow-ups alongside issue findings, providing the next execution step within a mandated output structure.

How does repository context affect planning for a GitHub issue?

Repository context affects planning by integrating nearby codebase state with live issue data to ensure the generated implementation plan is minimal, safe, and executable within the current code environment.

When should I not use automated planning for GitHub issues?

Avoid automated planning for GitHub issues when readiness criteria are unmet, as the Skill enforces escalation rules to keep planning scoped, safe, and guard-railed against incomplete or ambiguous issue data.