Issue Executor FAQs

Question 1

When should I use the Issue Executor in my workflow?

Accepted Answer

The best time to use this skill is at the very beginning of a task. Use it when you pick up a new issue from your sprint to ensure you have a clean git environment and a clear, AI-assisted roadmap before you write a single line of code.

Question 2

What are the main benefits of using this skill with Claude Code?

Accepted Answer

It improves developer productivity by reducing manual setup time, ensures 'Context is King' by pulling in relevant docs automatically, and enforces best practices like branch isolation and atomic work habits.

Question 3

How does this skill use Gemini AI?

Accepted Answer

It uses the Gemini CLI to perform high-level context synthesis. By feeding the AI your issue requirements, relevant documentation, and past project learnings, it creates a cohesive plan that avoids past mistakes and aligns with your project's specific standards.

Question 4

What exactly does the Issue Executor skill do?

Accepted Answer

Issue Executor automates the 'setup' phase of development. It fetches GitHub issue details, synthesizes them with project specifications and retrospectives using Gemini AI, generates a step-by-step implementation plan, and automatically creates a dedicated feature branch for your work.

Question 5

What tools do I need to have installed to use Issue Executor?

Accepted Answer

To function correctly, this skill requires the GitHub CLI (gh), the Gemini CLI, jq for JSON processing, and a standard Git installation. Your project should also follow a structured documentation format (e.g., a docs/ directory).

Issue Executor

Issue Executor

Key Features

Use Cases

Key Features

Use Cases