agentdev-issue-management

Provides safe procedures for creating, updating, linking, and verifying GitHub Issues.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-issue-management-yogata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentdev-issue-management
Source: https://github.com/yogata/agent-dev-flow/tree/main/src/opencode/skills/agentdev-issue-management
Command: npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-issue-management-yogata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? GitHub Issue operations performed by AI agents can silently corrupt content through encoding errors, broken Markdown tables, leftover placeholders, or one-directional parent/child links. This Skill supplies verified operational procedures that prevent these failures during Issue creation, update, and linking. ## Core Features & Use Cases - Safe Issue Operations: Standardized call format for issue_create, issue_update, and comment_create via the agentdev_gh custom tool, including double-quote avoidance and explicit labels arguments. - Post-Write Verification: Read-back comparison of written content covering encoding, Markdown structure, required template sections, and repository reference links, with a three-stage retry policy. - Parent/Child Link Validation: Bidirectional verification of Parent: #N links between Epic and child Issues, plus Epic status tracking table updates with single-writer constraints. - Use Case: When a case-open command creates an Epic Issue and child Issues, use this Skill to confirm each Issue body was written correctly, replace #{TBD} placeholders with real numbers, and verify both directions of the parent/child links before proceeding. ## Quick Start Ask the agent to create a GitHub Issue and verify the written content, parent/child links, and Epic status table using the safe Issue operation procedures.

Frequently Asked Questions about agentdev-issue-management

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

FAQPage Schema
How do I safely create and update GitHub Issues with an AI agent?▼

Use the agentdev_gh custom tool with the standard call format: avoid double quotes in titles and bodies, always pass the labels argument explicitly, and run a read-back verification after every write operation. Each create, update, or comment requires its own individual VERIFY step.

How to verify parent and child Issue links on GitHub?▼

Check that the child Issue body starts with `Parent: #N` matching the actual Epic number, then confirm the Epic body lists the child Issue number. Both directions must be verified; a one-directional check is not considered complete.

Why does GitHub Issue creation fail with a JSON parse error?▼

Long Issue bodies containing double quotes can break JSON parsing in the harness. Replace double quotes with backticks in the title and body, then retry; if it still fails, shorten the body before retrying again.

What should an Epic Issue status tracking table update include?▼

Take a snapshot of the table before updating, keep column counts consistent when adding rows, replace all #{TBD} placeholders with real numbers, and confirm totals equal in-progress plus completed counts. Only the case-close command may write to the Epic table.

When should this Skill not be used for Issue workflows?▼

Do not use it for deciding Epic/child creation order, selecting Issue body templates, or gh CLI encoding workarounds. Those belong to the case-open command, the agentdev-workflow-templates skill, and the agentdev_gh tool respectively.