ir:exec

Analyze a GitHub issue and generate a structured implementation plan.

93|10|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/ingo-eichhorst/Irrlicht --skill ir-exec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ir:exec
Source: https://github.com/ingo-eichhorst/Irrlicht/tree/main/.claude/skills/ir%3Aexec
Command: npx skills add https://github.com/ingo-eichhorst/Irrlicht --skill ir-exec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate GitHub issues and produce an actionable, startable implementation plan that kickstarts work in a fresh worktree.

Core Features & Use Cases

  • Extract requirements, constraints, and acceptance criteria from issues to inform engineering tasks.
  • Generate a structured plan comprising Problem, Approach, Steps, and Risks, ready for review.
  • Enter plan mode to present the plan for approval before coding (ExitPlanMode).

Quick Start

Provide the issue number or URL and I will generate a plan to implement it.

Frequently Asked Questions about ir:exec

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

FAQPage Schema
How do I generate an implementation plan from a GitHub issue?

You can generate an implementation plan by providing the GitHub issue number or URL, which triggers analysis of requirements and outputs a structured plan covering the problem, approach, steps, and risks.

What is the best way to plan GitHub issues before starting work in a fresh worktree?

Planning GitHub issues before starting in a fresh worktree involves extracting acceptance criteria from the issue and entering plan mode to present a structured implementation plan for approval before coding begins.

Can I extract acceptance criteria and constraints directly from a GitHub issue?

Yes, extracting acceptance criteria and constraints directly from a GitHub issue is possible by analyzing its content to identify key terms and modules, which then inform the actionable engineering tasks.

Does the generated plan require approval before coding starts?

Yes, the generated plan requires approval before coding starts because the tool enters plan mode to present the structured implementation steps for review via ExitPlanMode.

How do I identify key modules and requirements when analyzing a GitHub issue?

Identifying key modules and requirements when analyzing a GitHub issue is handled by coordinating exploration with Explore subagents to investigate the codebase and extract the necessary technical context.

What does a structured implementation plan for a GitHub issue include?

A structured implementation plan for a GitHub issue includes four main sections: the problem definition, the proposed approach, the actionable steps to take, and the potential risks involved.