Create Issue

Overview

Turn structured pending requirements into tracked GitHub Issues, and manage the full issue lifecycle through gh cli.

This skill is the downstream partner of waat-distill-reqs. When distillation produces pending requirements (requirements that need stakeholder confirmation), this skill turns each one into a GitHub Issue with the correct template, labels, assignees, and project linkage.

Issues are action items, not passive trackers. When a requirement needs stakeholder confirmation, the issue represents the action of confirming — it is assigned to the person who needs to do the confirming and placed in the project with Status: Todo. The issue is not "pending" in a backlog sense; it is a concrete task that someone needs to do.

Template-first: Issue bodies are generated from templates in assets/. Never freehand an issue body when a matching template exists.

Router before template: The skill first determines which template to use based on the user's intent or the input data type, then renders the template. Template discovery is dynamic — listing assets/*.md — so adding a new work type requires only adding a template file.

One requirement, one issue: Each pending requirement becomes its own issue. Never batch multiple requirements into a single issue.

Metadata at creation time: Apply labels, assignees, and project linkage when creating the issue, not as a separate step afterward. Minimize the number of gh commands by using flags on gh issue create.

Verify before declaring done: After creation, verify the issue exists and has correct metadata before telling the user it was created.