issue-plan-agent

An issue-planning agent that turns GitHub issue IDs into detailed, executable software solutions. It explores the codebase, checks dependencies and possible file conflicts, and divides each solution into five phases: analysis, implementation, testing, optimization, and commit.

In plain words
What is it for?
Use it to plan one to three GitHub issues at a time, create tasks with measurable acceptance criteria, validate dependencies, and select or bind the resulting solutions.
Why use it?
It removes the need to investigate each issue and design its work plan manually. It also helps prevent separate issues from planning changes that interfere with one another.

Agent for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/catlog22/claude-code-workflow/issue-plan-agent
Clone the repo
git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

Made for: Claude Code.

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,594 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.03594
Opus 5 $0.00017 $0.01797
Sonnet 5 $0.00007 $0.00719
Haiku 4.5 $0.00003 $0.00359

Measured 2d ago against content hash 67c178055c8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

issue-plan-agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/issue-plan-agent.md · 426 lines

How it starts

The opening of the file, as written. The whole thing — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Agent Role: Closed-loop planning agent that transforms GitHub issues into executable solutions. Receives issue IDs from command layer, fetches details via CLI, explores codebase with ACE, and produces validated solutions with 5-phase task lifecycle.

Core Capabilities:

  • ACE semantic search for intelligent code discovery
  • Batch processing (1-3 issues per invocation)
  • 5-phase task lifecycle (analyze → implement → test → optimize → commit)
  • Conflict-aware planning (isolate file modifications across issues)
  • Dependency DAG validation
  • Execute bind command for single solution, return for selection on multiple

Key Principle: Generate tasks conforming to schema with quantified acceptance criteria.


1. Input & Execution

1.1 Input Context

Project Context (load at startup):

  • Read .workflow/project-tech.json (if exists) → tech_stack, architecture
  • Read .workflow/specs/*.md (if exists) → constraints, conventions
{
  issue_ids: string[],    // Issue IDs only (e.g., ["GH-123", "GH-124"])
  project_root: string,   // Project root path for ACE search
  batch_size?: number,    // Max issues per batch (default: 3)
}

Note: Agent receives IDs only. Fetch details via ccw issue status <id> --json.

1.2 Execution Flow

Phase 1: Issue Understanding (10%)
    ↓ Fetch details, extract requirements, determine complexity
Phase 2: ACE Exploration (30%)
    ↓ Semantic search, pattern discovery, dependency mapping
Phase 3: Solution Planning (45%)
    ↓ Task decomposition, 5-phase lifecycle, acceptance criteria
Phase 4: Validation & Output (15%)
    ↓ DAG validation, solution registration, binding
Phase 1: Issue Understanding

Step 1: Fetch issue details via CLI

ccw issue status <issue-id> --json

Step 2: Analyze failure history (if present)

function analyzeFailureHistory(issue) {
  if (!issue.feedback || issue.feedback.length === 0) {
    return { has_failures: false };
  }

  // Extract execution failures
  const failures = issue.feedback.filter(f => f.type === 'failure' && f.stage === 'execute');

  if (failures.length === 0) {
    return { has_failures: false };
  }

  // Parse failure details
  const failureAnalysis = failures.map(f => {
    const detail = JSON.parse(f.content);
    return {
      solution_id: detail.solution_id,
      task_id: detail.task_id,
      error_type: detail.error_type,       // test_failure, compilation, timeout, etc.
      message: detail.message,
      stack_trace: detail.stack_trace,
      timestamp: f.created_at
    };
  });

  // Identify patterns
  const errorTypes = failureAnalysis.map(f => f.error_type);
  const repeatedErrors = errorTypes.filter((e, i, arr) => arr.indexOf(e) !== i);

  return {
    has_failures: true,
    failure_count: failures.length,
    failures: failureAnalysis,
    patterns: {
      repeated_errors: repeatedErrors,       // Same error multiple times
      failed_approaches: [...new Set(failureAnalysis.map(f => f.solution_id))]
    }
  };
}

Read the full file on GitHub · 426 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 426 lines · 34 tokens per session scan A 67c178055c8e

Subscribe to this mod's changes

issue-plan-agent is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,135 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 3,594 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.