agentdev-workflow-issue

Manages tracking issues on GitHub through natural language instructions and conversation context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the need to learn GitHub subcommands, label names, or issue field schemas when recording and managing unresolved questions during development, by interpreting natural language instructions and conversation context to operate tracking issues. ## Core Features & Use Cases - Operation Type Detection: Determines whether to create, search, update, hold, resolve, close, or reopen a tracking issue based on the user's instruction and conversation state. - Issue Creation Judgment: Checks whether an unresolved matter is worth filing, attempts resolution first, and searches existing issues to avoid duplicates. - Tool-Contract-Based Execution: Performs all reads and writes through the agentdev_gh custom tool, supporting both GitHub issues and local issue environments without direct file or git operations. - Use Case: During a design discussion, tell the agent to record an unresolved trade-off as a tracking issue; it checks for duplicates, files the issue, and later updates its state as the discussion progresses toward resolution. ## Quick Start Ask the agent via the /agentdev/issue command to record the current unresolved question as a tracking issue.

Frequently Asked Questions about agentdev-workflow-issue

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

FAQPage Schema
How do I create a tracking issue from a conversation?▼

Invoke the /agentdev/issue command with a natural language instruction such as asking to record an unresolved matter. The workflow judges whether it is worth filing, searches for duplicates, and creates the issue through the agentdev_gh tool.

How does the skill decide which issue operation to run?▼

It infers the operation type from your instruction, conversation context, and the target issue's current state, mapping to actions like create, search, update, hold, resolve, close, or reopen. If the intent is ambiguous, it asks for confirmation instead of guessing.

Does it work without GitHub, in a local environment?▼

Yes, it supports a local issue environment where the agentdev_gh tool persists local issues. The workflow itself performs no direct file writes or git operations in either mode.

Can it update requirements or design documents directly?▼

No, it is prohibited from directly updating canonical artifacts like requirements or designs. Resolution results are delegated to the capability that owns the target artifact, and the reflection target is recorded in the issue body.

When should I not use this workflow?▼

Do not use it for Case Issue operations, which belong to case-open, case-run, case-close, and case-revise, or for turning a tracking issue directly into execution work. Execution requires the formal requirements path such as req-define and case-open.