A command that investigates issues and creates an implementation plan for each one. An issue is a recorded problem or request, and a solution is the proposed set of work that addresses it.

Use it to turn pending issues into planned work, inspect the code involved, and bind each issue to one selected solution when alternatives exist.

It combines investigation and planning in one workflow, reducing the need to manually connect a problem to an actionable solution.

plan — Command for Claude Code by catlog22/Claude-Code-Workflow

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.

Clone the repo

git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/plan/github.svg)](https://agentmods.dev/commands/catlog22/claude-code-workflow/plan)

Your own site

<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/plan"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/catlog22/claude-code-workflow/plan"><img src="https://agentmods.dev/badge/commands/catlog22/claude-code-workflow/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 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,137 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.03137
Opus 5.5	$0.00007	$0.01255
Sonnet 5.5	$0.00004	$0.00627
Haiku 4.5	$0.00002	$0.00314

Measured 1mo ago against content hash f39e10bd66ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan 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 1mo 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/commands/issue/plan.md · 344 lines

How it starts

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

Auto Mode

When --yes or -y: Auto-bind solutions without confirmation, use recommended settings.

Issue Plan Command (/issue:plan)

Overview

Unified planning command using issue-plan-agent that combines exploration and planning into a single closed-loop workflow.

Behavior:

Single solution per issue → auto-bind
Multiple solutions → return for user selection
Agent handles file generation

Core Guidelines

⚠️ Data Access Principle: Issues and solutions files can grow very large. To avoid context overflow:

Operation	Correct	Incorrect
List issues (brief)	`ccw issue list --status pending --brief`	`Read('issues.jsonl')`
Read issue details	`ccw issue status <id> --json`	`Read('issues.jsonl')`
Update status	`ccw issue update <id> --status ...`	Direct file edit
Bind solution	`ccw issue bind <id> <sol-id>`	Direct file edit

Output Options:

--brief: JSON with minimal fields (id, title, status, priority, tags)
--json: Full JSON (agent use only)

Orchestration vs Execution:

Command (orchestrator): Use --brief for minimal context
Agent (executor): Fetch full details → ccw issue status <id> --json

ALWAYS use CLI commands for CRUD operations. NEVER read entire issues.jsonl or solutions/*.jsonl directly.

Usage

/issue:plan [<issue-id>[,<issue-id>,...]] [FLAGS]

# Examples
/issue:plan                           # Default: --all-pending
/issue:plan GH-123                    # Single issue
/issue:plan GH-123,GH-124,GH-125      # Batch (up to 3)
/issue:plan --all-pending             # All pending issues (explicit)

# Flags
--batch-size <n>      Max issues per agent batch (default: 3)

Execution Process

Phase 1: Issue Loading & Intelligent Grouping
   ├─ Parse input (single, comma-separated, or --all-pending)
   ├─ Fetch issue metadata (ID, title, tags)
   ├─ Validate issues exist (create if needed)
   └─ Intelligent grouping via Gemini (semantic similarity, max 3 per batch)

Phase 2: Unified Explore + Plan (issue-plan-agent)
   ├─ Launch issue-plan-agent per batch
   ├─ Agent performs:
   │   ├─ ACE semantic search for each issue
   │   ├─ Codebase exploration (files, patterns, dependencies)
   │   ├─ Solution generation with task breakdown
   │   └─ Conflict detection across issues
   └─ Output: solution JSON per issue

Phase 3: Solution Registration & Binding
   ├─ Append solutions to solutions/{issue-id}.jsonl
   ├─ Single solution per issue → auto-bind
   ├─ Multiple candidates → AskUserQuestion to select
   └─ Update issues.jsonl with bound_solution_id

Phase 4: Summary
   ├─ Display bound solutions
   ├─ Show task counts per issue
   └─ Display next steps (/issue:queue)

Read the full file on GitHub · 344 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.

1mo ago First seen · 344 lines · 18 tokens per session scan A f39e10bd66ba

Subscribe to this mod's changes

plan is a command published in the GitHub repository catlog22/Claude-Code-Workflow (2,125 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 3,137 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Planning Project management claude cli-tools codex context-management gemini-cli

plan

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Auto Mode

Issue Plan Command (/issue:plan)

Overview

Core Guidelines

Usage

Execution Process

What this file has done since we first saw it

Other commands, from other repositories

session-list

jira

wtfp:contribute

gofer_hydrate

gofer:check-workspace

bulk-import-issues