IS

Menu-driven issue management system for tracking tasks and solutions.

Install

mkdir -p .claude/skills/issue-manage && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2741" && unzip -o skill.zip -d .claude/skills/issue-manage && rm skill.zip

Installs to .claude/skills/issue-manage

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Interactive issue management with menu-driven CRUD operations. Use when managing issues, viewing issue status, editing issue fields, performing bulk operations, or viewing issue history. Triggers on "manage issue", "list issues", "edit issue", "delete issue", "bulk update", "issue dashboard", "issue history", "completed issues".
330 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Beginner

Key capabilities

  • List active issues with filters
  • View detailed information for a specific issue
  • Modify fields of an existing issue
  • Delete issues with confirmation
  • View a history of completed issues
  • Perform batch operations on multiple issues

How it works

The skill provides a menu-driven interface to perform CRUD operations on issues, manage queues, and view issue history, interacting with JSONL files for persistence.

Inputs & outputs

You give it
User commands or selections via an interactive menu
You get back
Displayed issue lists, detailed issue views, or updated issue records

When to use issue-manage

  • Listing active project tasks
  • Bulk updating issue statuses
  • Viewing history of completed tasks

About this skill

Issue Management Skill

Interactive menu-driven interface for issue CRUD operations via ccw issue CLI.

Quick Start

Ask me:

  • "Show all issues" → List with filters
  • "View issue GH-123" → Detailed inspection
  • "Edit issue priority" → Modify fields
  • "Delete old issues" → Remove with confirmation
  • "Bulk update status" → Batch operations
  • "Show completed issues" → View issue history
  • "Archive old issues" → Move to history

CLI Endpoints

# Core operations
ccw issue list                      # List active issues
ccw issue list <id> --json          # Get issue details
ccw issue history                   # List completed issues (from history)
ccw issue history --json            # Completed issues as JSON
ccw issue status <id>               # Detailed status
ccw issue init <id> --title "..."   # Create issue
ccw issue task <id> --title "..."   # Add task
ccw issue bind <id> <solution-id>   # Bind solution
ccw issue update <id> --status completed  # Complete & auto-archive

# Solution queries
ccw issue solution <id>             # List solutions for a single issue
ccw issue solution <id> --brief     # Brief: solution_id, files_touched, task_count
ccw issue solutions                 # Batch list all bound solutions
ccw issue solutions --status planned --brief  # Filter by issue status

# Queue management
ccw issue queue                     # List current queue
ccw issue queue add <id>            # Add to queue
ccw issue queue list                # Queue history
ccw issue queue switch <queue-id>   # Switch queue
ccw issue queue archive             # Archive queue
ccw issue queue delete <queue-id>   # Delete queue
ccw issue next                      # Get next task
ccw issue done <queue-id>           # Mark completed
ccw issue update --from-queue       # Sync statuses from queue

Operations

1. LIST 📋

Filter and browse issues:

┌─ Filter by Status ─────────────────┐
│ □ All        □ Registered          │
│ □ Planned    □ Queued              │
│ □ Executing  □ Completed           │
└────────────────────────────────────┘

Flow:

  1. Ask filter preferences → ccw issue list --json
  2. Display table: ID | Status | Priority | Title
  3. Select issue for detail view

2. VIEW 🔍

Detailed issue inspection:

┌─ Issue: GH-123 ─────────────────────┐
│ Title: Fix authentication bug       │
│ Status: planned | Priority: P2      │
│ Solutions: 2 (1 bound)              │
│ Tasks: 5 pending                    │
└─────────────────────────────────────┘

Flow:

  1. Fetch ccw issue status <id> --json
  2. Display issue + solutions + tasks
  3. Offer actions: Edit | Plan | Queue | Delete

3. EDIT ✏️

Modify issue fields:

FieldOptions
TitleFree text
PriorityP1-P5
Statusregistered → completed
ContextProblem description
LabelsComma-separated

Flow:

  1. Select field to edit
  2. Show current value
  3. Collect new value via AskUserQuestion
  4. Update .workflow/issues/issues.jsonl

4. DELETE 🗑️

Remove with confirmation:

⚠️ Delete issue GH-123?
This will also remove:
- Associated solutions
- Queued tasks

[Delete] [Cancel]

Flow:

  1. Confirm deletion via AskUserQuestion
  2. Remove from issues.jsonl
  3. Clean up solutions/<id>.jsonl
  4. Remove from queue.json

5. HISTORY 📚

View and manage completed issues:

┌─ Issue History ─────────────────────┐
│ ID                 Completed   Title │
│ ISS-001  2025-12-28 12:00   Fix bug │
│ ISS-002  2025-12-27 15:30   Feature │
└──────────────────────────────────────┘

Flow:

  1. Fetch ccw issue history --json
  2. Display table: ID | Completed At | Title
  3. Optional: Filter by date range

Auto-Archive: When issue status → completed:

  • Issue moves from issues.jsonlissue-history.jsonl
  • Solutions remain in solutions/<id>.jsonl
  • Queue items marked completed

6. BULK 📦

Batch operations:

OperationDescription
Update StatusChange multiple issues
Update PriorityBatch priority change
Add LabelsTag multiple issues
Delete MultipleBulk removal
Queue All PlannedAdd all planned to queue
Retry All FailedReset failed tasks
Sync from QueueUpdate statuses from active queue

Workflow

┌────────────────────────────────────────────────┐
│              Main Menu                          │
│  ┌────┐ ┌────┐ ┌────┐ ┌─────┐ ┌────┐          │
│  │List│ │View│ │Edit│ │Hist.│ │Bulk│          │
│  └──┬─┘ └──┬─┘ └──┬─┘ └──┬──┘ └──┬─┘          │
└─────┼──────┼──────┼──────┼───────┼─────────────┘
      │      │      │      │       │
      ▼      ▼      ▼      ▼       ▼
   Filter  Detail  Fields  History Multi
   Select  Actions Update  Browse  Select
      │      │      │      │       │
      └──────┴──────┴──────┴───────┘
                    │
                    ▼
             Back to Menu

Issue Lifecycle:

registered → planned → queued → executing → completed
                                               │
                                               ▼
                                    issue-history.jsonl

Implementation Guide

Entry Point

// Parse input for issue ID
const issueId = input.match(/^([A-Z]+-\d+|ISS-\d+)/i)?.[1];

// Show main menu
await showMainMenu(issueId);

Main Menu Pattern

// 1. Fetch dashboard data
const issues = JSON.parse(Bash('ccw issue list --json') || '[]');
const history = JSON.parse(Bash('ccw issue history --json 2>/dev/null') || '[]');
const queue = JSON.parse(Bash('ccw issue queue --json 2>/dev/null') || '{}');

// 2. Display summary
console.log(`Active: ${issues.length} | Completed: ${history.length} | Queue: ${queue.pending_count || 0} pending`);

// 3. Ask action via AskUserQuestion
const action = AskUserQuestion({
  questions: [{
    question: 'What would you like to do?',
    header: 'Action',
    options: [
      { label: 'List Issues', description: 'Browse active issues' },
      { label: 'View Issue', description: 'Detail view (includes history)' },
      { label: 'Edit Issue', description: 'Modify fields' },
      { label: 'Bulk Operations', description: 'Batch actions' }
    ]
  }]
});

// 4. Route to handler

Filter Pattern

const filter = AskUserQuestion({
  questions: [{
    question: 'Filter by status?',
    header: 'Filter',
    multiSelect: true,
    options: [
      { label: 'All', description: 'Show all' },
      { label: 'Registered', description: 'Unplanned' },
      { label: 'Planned', description: 'Has solution' },
      { label: 'Executing', description: 'In progress' }
    ]
  }]
});

Edit Pattern

// Select field
const field = AskUserQuestion({...});

// Get new value based on field type
// For Priority: show P1-P5 options
// For Status: show status options
// For Title: accept free text via "Other"

// Update file
const issuesPath = '.workflow/issues/issues.jsonl';
// Read → Parse → Update → Write

Data Files

FilePurpose
.workflow/issues/issues.jsonlActive issue records
.workflow/issues/issue-history.jsonlCompleted issues (archived)
.workflow/issues/solutions/<id>.jsonlSolutions per issue
.workflow/issues/queues/index.jsonQueue index (multi-queue)
.workflow/issues/queues/<queue-id>.jsonIndividual queue files

Error Handling

ErrorResolution
No issues foundSuggest /issue:new to create
Issue not foundShow available issues, re-prompt
Write failureCheck file permissions
Queue errorDisplay ccw error message

Related Commands

  • /issue:new - Create structured issue
  • /issue:plan - Generate solution
  • /issue:queue - Form execution queue
  • /issue:execute - Execute tasks

Limitations

  • Issue data is stored in `.workflow/issues/issues.jsonl` and related files.
  • Solutions remain in `solutions/<id>.jsonl` after an issue is archived.

How it compares

This skill offers a menu-driven CLI for issue management, providing structured workflows for common operations like bulk updates and history tracking, unlike manual file editing.

Compared to similar skills

issue-manage side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
issue-manage (this skill)25moReviewBeginner
github-project-management46moReviewAdvanced
prepare04moNo flagsIntermediate
jira116moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

github-project-management

ruvnet

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

427

prepare

This-Is-NPC

Create implementation preparation artifacts from approved requirements. Use when a user asks to convert requirements into a project management issue and generate or create the implementation branch using workflow naming rules.

00

jira

davila7

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

1152

task-master

sfc-gh-dflippo

AI-powered task management for structured, specification-driven development. Use this skill when you need to manage complex projects with PRDs, break down tasks into subtasks, track dependencies, and maintain organized development workflows across features and branches.

22131

create-plans

glittercowboy

Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that Claude will execute. Produces Claude-executable plans with verification criteria, not enterprise documentation. Handles briefs, roadmaps, phase plans, and context handoffs.

15

create-issue

dotCMS

Create GitHub issues using repository templates. Use when the user asks to create an issue, bug report, feature request, task, spike, epic, or UX requirement. Also use when the user describes a problem, bug, enhancement, or work item that should be tracked. Supports both English and Spanish input.

13

Search skills

Search the agent skills registry