Draft GitHub Issue

This documentation was generated with the assistance of AI. Please report any inaccuracies.

Write a fully specified GitHub issue the way a specification is written: grounded in the codebase, complete, reviewed for gaps before it exists, and split into dependency-ordered sub-issues when it is too large.

Purpose

iru-draft-github-issue is the detailed counterpart to the quick Create GitHub Issue path. It explores the codebase, decides whether the issue is functional (context, functional requirements, acceptance criteria, optional technical details, out of scope, dependencies, task details) or documentation (audience, technical vs. non-technical page structure, diagrams, bibliography, acceptance criteria), interviews the user, writes the draft to a file and then loops (at most five rounds) with Review GitHub Issue, resolving findings from the codebase first and asking the user for the rest. When the issue looks too large it offers Split GitHub Issue. Nothing is created on GitHub until the user confirms the final draft. It stops on non-GitHub hosts. Use it for detailed, spec-style issues (Create GitHub Issue stays the quick path for a simple one); for issues that already exist use Review GitHub Issue or Split GitHub Issue instead.

Purpose group

Ticket Intake

Plugin

Shipped by the iru-core plugin of the ai-catalog marketplace (install with /plugin install iru-core@ai-catalog; see Plugins).

Invocation

/iru-draft-github-issue
/iru-draft-github-issue functional
/iru-draft-github-issue documentation
/iru-draft-github-issue functional <short description>

Inputs

Argument Required Description Default

Argument	Required	Description	Default
`kind`	No	`functional` or `documentation`, as the first word of the arguments.	Inferred when unambiguous, otherwise asked.
`short description`	No	Starting point for the issue; only what it leaves unclear is asked.	None; the interview asks.

kind

functional or documentation, as the first word of the arguments.

Inferred when unambiguous, otherwise asked.

short description

Starting point for the issue; only what it leaves unclear is asked.

None; the interview asks.

Outputs

A draft file for the issue, revised through the review loop.
If the user confirms: a new GitHub issue (or, if a split was accepted, the root issue, sub-issues and milestone created by iru-split-github-issue, which receives the chosen label as label:).
A final report with the issue number and URL.
If the user declines, no issue is created and the draft remains the deliverable.

Execution flow

flowchart TD A["Start"] --> B{Hosted on GitHub?} B -- no --> Z["Stop: GitHub only"] B -- yes --> C["iru-explore"] C --> D["Decide kind\n(functional / documentation)"] D --> E["Interview user"] E --> F["Optional context, due date,\nimportance, label"] F --> G["Write draft file"] G --> H["Review loop, max 5 rounds\n(iru-review-github-issue)"] H --> I{Too large?} I -- split --> J["iru-split-github-issue"] I -- keep --> K["Show draft + confirm"] J --> K K -- confirmed --> L["Create issue"] K -- declined --> M["Stop: draft is the deliverable"] L --> N["Report"]

Dependencies

Invokes

Explore - Step 2, general orientation to ground the draft.
Review GitHub Issue - Step 7, the automatic review loop over the draft file.
Split GitHub Issue - Step 8, offered when the issue is too large.

Invoked by

None of this repository’s skills; a top-level entry point run directly by a person.

Related agents

None; iru-draft-github-issue does not spawn any agent.

Source

SKILL.md on GitHub - the file this page was generated from.