issue-manage
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.zipInstalls 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".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
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:
- Ask filter preferences →
ccw issue list --json - Display table: ID | Status | Priority | Title
- 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:
- Fetch
ccw issue status <id> --json - Display issue + solutions + tasks
- Offer actions: Edit | Plan | Queue | Delete
3. EDIT ✏️
Modify issue fields:
| Field | Options |
|---|---|
| Title | Free text |
| Priority | P1-P5 |
| Status | registered → completed |
| Context | Problem description |
| Labels | Comma-separated |
Flow:
- Select field to edit
- Show current value
- Collect new value via AskUserQuestion
- 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:
- Confirm deletion via AskUserQuestion
- Remove from
issues.jsonl - Clean up
solutions/<id>.jsonl - 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:
- Fetch
ccw issue history --json - Display table: ID | Completed At | Title
- Optional: Filter by date range
Auto-Archive: When issue status → completed:
- Issue moves from
issues.jsonl→issue-history.jsonl - Solutions remain in
solutions/<id>.jsonl - Queue items marked completed
6. BULK 📦
Batch operations:
| Operation | Description |
|---|---|
| Update Status | Change multiple issues |
| Update Priority | Batch priority change |
| Add Labels | Tag multiple issues |
| Delete Multiple | Bulk removal |
| Queue All Planned | Add all planned to queue |
| Retry All Failed | Reset failed tasks |
| Sync from Queue | Update 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
| File | Purpose |
|---|---|
.workflow/issues/issues.jsonl | Active issue records |
.workflow/issues/issue-history.jsonl | Completed issues (archived) |
.workflow/issues/solutions/<id>.jsonl | Solutions per issue |
.workflow/issues/queues/index.json | Queue index (multi-queue) |
.workflow/issues/queues/<queue-id>.json | Individual queue files |
Error Handling
| Error | Resolution |
|---|---|
| No issues found | Suggest /issue:new to create |
| Issue not found | Show available issues, re-prompt |
| Write failure | Check file permissions |
| Queue error | Display 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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| issue-manage (this skill) | 2 | 5mo | Review | Beginner |
| github-project-management | 4 | 6mo | Review | Advanced |
| prepare | 0 | 4mo | No flags | Intermediate |
| jira | 11 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by catlog22
View all by catlog22 →You might also like
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
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.
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.
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.
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.
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.