create-issue

Create Github Issue

Purpose

This command generates {{scm.provider}} issues with a clean, actionable, well-structured format. It is optimized for creating consistent {{scm.provider}} issues for engineering planning, with consistent formatting across feat, fix, chore, docs, and epic types.

Command Name

create-issue

Invocation Syntax

You can invoke this command with optional flags:

/create-github-issue [flags] <description>

Flags

• -b, --board <name>: Specify project board (default: "{{project.board}}")
• -l, --label <label>: Add labels to the issue (can be used multiple times)
• --prompt: Enable interactive mode (prompts for board and labels if supported)
• --local: Save the issue as a local markdown file in the plans/ directory instead of creating a {{scm.provider}} issue

Examples

# Basic issue creation (no board or labels)
/create-github-issue feat(web): add control family status card

# With project board
/create-github-issue --board "Tech Debt" fix(api): memory leak in cache

# With labels
/create-github-issue -l bug -l priority:high fix(security): patch vulnerability

# Multiple labels and board
/create-github-issue -b "Backend" -l enhancement -l good-first-issue feat(api): add new endpoint

# Interactive mode for teams with complex configurations
/create-github-issue --prompt feat(web): new feature requiring custom setup

# Save locally as a markdown file in plans/ (private, no GitHub issue created)
/create-github-issue --local feat(web): new feature to plan privately

{{- if .agent.plan_mode.enabled }}

1. Immediately {{agent.plan_mode.enter}} when this command is invoked
2. Parse the user input to extract flags and issue description
3. Format the {{scm.provider}} issue using the exact markdown structure below
4. Use {{agent.plan_mode.exit}} to present the formatted issue as the plan
5. Wait for user approval before proceeding
6. After approval:
   • If --prompt flag is present: Use interactive mode (ask for board and labels if repository supports them)
   • Otherwise: Use parsed flags only (no prompting, no automatic assignments)
7. Execute the {{scm.provider}} CLI commands to create the issue with configured settings {{- else }}
8. Parse the user input to extract flags and issue description
9. Format the {{scm.provider}} issue using the exact markdown structure below
10. Present the formatted issue for user review
11. Wait for user approval before proceeding
12. After approval:
    • If --prompt flag is present: Use interactive mode (ask for board and labels if repository supports them)
    • Otherwise: Use parsed flags only (no prompting, no automatic assignments)
13. Execute the {{scm.provider}} CLI commands to create the issue with configured settings {{- end }}