Inputs

•Title (required)
•Body content (required) — used to fill the template below
•Labels (optional)
•Milestone (optional)
•Parent issue number (optional) — set as parent (sub-issue)

Issue body template

Compose the issue body using this template exactly. Fill in each section from the user's input.

markdown

## Overview

<!-- A concise summary of the issue. -->

## Goal

<!-- The purpose and success criteria. What should be achieved and how will completion be measured? -->

## Context

<!-- Background information, current state, and any related decisions or discussions. -->

## Expected Impact

<!-- The expected outcomes and benefits of resolving this issue. -->

## Acceptance Criteria

- [ ] <!-- Specific, verifiable condition -->

## References

<!-- Links to related documents, PRs, discussions, or external resources. -->

## Implementation ideas

<!-- Initial ideas on how this could be implemented. -->

> **Note**: These are preliminary thoughts at issue creation time and have not been thoroughly considered from an implementation perspective. During design, revisit the goal and re-evaluate the approach from scratch.

Procedure

•
Gather title, body content, and optional inputs from the user.
•
Search for duplicates and related issues with gh issue list -s open -S "<keywords>".
- •If a potential duplicate exists, inform the user and ask how to proceed.
- •If related issues exist, suggest parent-child relationships to the user.
•
Compose the issue body using the template above.

•

Create the issue:

gh issue create --title "<title>" --body "<body>" --assignee "nownabe" [--label "<label>"] [--milestone "<milestone>"]

•

If a parent issue is applicable, verify it is open and link via the REST API:

SUB_ISSUE_ID=$(gh api "repos/{owner}/{repo}/issues/<number>" --jq '.id')
gh api "repos/{owner}/{repo}/issues/<parent-number>/sub_issues" -X POST -f "sub_issue_id=$SUB_ISSUE_ID"

•
Return the created issue URL to the user.