manage-issue

Create, list, update, close, and link issues in a JSONL store.

511|63|Updated Mar 17, 2026

Search Tags:#workflow #cli #issues #issue-tracking #jsonl #bug-tracking #task-linking

Ready to run

npx skills add https://github.com/catlog22/Maestro-Flow --skill manage-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: manage-issue
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/manage-issue
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill manage-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a lightweight local issue CRUD system so teams can create, inspect, update, close, and link issues to tasks without relying on an external tracker.

Core Features & Use Cases

Create issues with schema-driven prompts and autogenerated IDs (ISS-{YYYYMMDD}-{NNN}) for consistent tracking.
List and filter issues by status, severity, phase, and source stored in a JSONL-based datastore.
Update, close, and archive issues with timestamps and resolution handling, and link issues bidirectionally to task JSONs to maintain cross-references.
Use Case: Quickly record a newly discovered authentication bug, tag it as high severity, link it to an existing task, and later close it with a resolution note.

Quick Start

Use the manage-issue skill to create a new high-severity issue titled Auth token expiry bug.

Frequently Asked Questions about manage-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track local project issues without an external bug tracker?▼

Track local project issues by operating on a .workflow/issues JSONL datastore to create, list, and close records without relying on an external bug tracker. It generates standardized IDs and moves closed items to an issue-history archive to maintain a clean active list.

How do I create a new issue and link it to an existing task?▼

Create a new issue using schema-driven prompts that generate an ID like ISS-{YYYYMMDD}-{NNN}. Link issues bidirectionally to task JSONs to maintain cross-references, ensuring task records and issue records point to each other.

Can I filter issues by severity and status in a JSONL datastore?▼

List and filter issues by status, severity, phase, and source stored in the JSONL-based datastore. This allows targeted queries to find high-severity bugs or active tasks within the local tracking system.

What happens to closed issues in the local issue tracking workflow?▼

Closed issues are updated with timestamps and resolution notes, then moved to an issue-history archive. This maintains issue history by keeping the active JSONL datastore clean while preserving past bug tracking records.

Do I need any external dependencies to manage issue records locally?▼

No external dependencies are required to manage issue records locally. The system operates entirely on a local JSONL store within the .workflow directory, handling validation and error codes internally.

How does issue linking work when connecting bugs to project tasks?▼

Issue linking updates bidirectional task-issue links by modifying both the issue record and the task JSON. This ensures cross-references remain synchronized when connecting a newly discovered bug to an existing project task.