Get parent issue Node ID

Create a GitHub Issue for yamada-ui.

Workflow

Use tools to interact with the user throughout the process.

1. Enter planning mode (required)

• Enter planning mode immediately — present and confirm a plan with the user before executing any side effects

2. Discover available templates

• Autonomously locate the .github/ISSUE_TEMPLATE/ directory in the repository and list English templates (excluding .ja.yml files)
• Read each template file to understand its name and required fields

3. Assess available context

• Evaluate whether the current conversation (arguments, prior messages) already contains enough information to draft the issue without asking the user:
  • Issue type can be determined (e.g., bug, feature, docs)
  • A clear title and description can be constructed
  • PR intent can be inferred (e.g., the user said "I'll fix it" → Yes; no mention → default to No)
• If sufficient context exists: skip steps 4 and 5, proceed directly to step 6 using the inferred values. Do not ask the user for information that is already present.
• If context is insufficient: follow steps 4 and 5 to collect the missing information interactively.

4. Confirm issue type (skip if context is sufficient)

• Present the available templates to the user and ask which type fits their need
• Suggest the appropriate type if unclear

5. Collect information (skip fields already known from context)

• Ask for all required fields from the selected template

• Ask follow-up questions to gather concrete details, code snippets, and URLs

• For the "PR intent" field, offer three options (separate from the template's Yes/No):

  Option	Description	Template value	Label
  Yes	Will create a PR	Yes	none
  No	Will not create a PR	No	triage
  Open to contributors	Open as a community contribution opportunity	Yes	good first issue