issue

Convert planning documents into GitHub issues with lifecycle management.

121|3|Updated Jan 13, 2022

Search Tags:#automation #workflow #github #issues #rfc #labeling #planning-docs

Ready to run

npx skills add https://github.com/jiangzhe/doradb --skill issue-jiangzhe

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates GitHub Issues lifecycle management from planning documents into trackable issues.

Core Features & Use Cases

Create, triage, assign, update, link, and close issues directly from docs/tasks and docs/rfcs.
Enforce non-interactive usage and deterministic workflows with labels and priorities, including RFC-specific prechecks.
Use planning documents as source of truth to ensure traceability and progress tracking across the project.

Quick Start

Create an issue from docs/tasks/000001-example.md using the non-interactive scripts

Frequently Asked Questions about issue

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

FAQPage Schema

How do I automate GitHub Issues creation from planning docs?▼

Automate GitHub Issues creation by converting planning documents into trackable issues using non-interactive scripts. The workflow processes docs/tasks and docs/rfcs files, enforcing deterministic label and priority validation to ensure auditable issue lifecycle management directly from your source documents.

Can I manage the entire GitHub Issues lifecycle from RFC documents?▼

Yes, GitHub Issues lifecycle management from RFC documents covers creation, triage, assignment, updating, linking, and closing. The process enforces RFC-specific prechecks and label validation to ensure safe, auditable workflows when converting docs/rfcs into trackable issues.

What is a planning-doc driven workflow for GitHub Issues?▼

A planning-doc driven workflow uses docs/tasks and docs/rfcs as the source of truth for GitHub Issues. This approach converts planning documents into trackable issues, ensuring traceability and progress tracking across the project through deterministic, non-interactive scripts.

Does the GitHub Issues automation validate labels and priorities?▼

Yes, GitHub Issues automation enforces label and priority validation during issue creation and updates. This deterministic validation ensures safe, auditable workflows and prevents inconsistent issue triage when converting planning documents into trackable issues.

How do I link and close GitHub Issues from planning documents?▼

Link and close GitHub Issues from planning documents by running non-interactive scripts that process docs/tasks and docs/rfcs files. The automation enforces deterministic workflows with label and priority validation to ensure safe, auditable issue lifecycle management.

Do I need interactive input to triage GitHub Issues from docs/tasks?▼

No, triaging GitHub Issues from docs/tasks requires no interactive input. The automation enforces non-interactive usage with deterministic workflows, executing label and priority validation through scripts to ensure safe, auditable issue management.