Create Task

---

description: Create a GitHub issue with project board integration

Create Task

Create a GitHub issue with full metadata and optional project board integration.

Usage

• create-task - Interactive guided issue creation
• create-task Add dark mode support - Pre-fill the title/description from arguments

Process

Follow these steps **in order**. Ask the user to gather all required info before creating anything.

Step 1: Detect the GitHub owner

Try to infer the GitHub owner/org from the current repository:

gh repo view --json owner --jq '.owner.login'

• If this succeeds, use the detected owner and confirm with the user.
• If this fails (e.g., not in a git repo), ask the user for the GitHub owner/org name.

Store this as `` for all subsequent commands.

Step 2: Ask which project

Fetch the list of projects dynamically:

gh project list --owner  --format json --jq '.projects[] | "\(.number) \(.title)"'

Then ask the user to select a project. Include a "None (no project)" option.

Step 3: Ask for repo, title, assignee, description, and content style

Ask these in a single question block if possible:

1. **Repository** - List repos from the owner. Run:

   gh repo list  --json name --jq '.[].name' --limit 50

   Let user select one.

2. **Title** - Ask for the issue title (free text).

3. **Assignee** - Fetch collaborators/members dynamically:

   gh api repos///collaborators --jq '.[].login'

   Let user select from the list. Allow multiple selections. Include an "Unassigned" option.

4. **Description/Body** - Ask for the issue body content (free text). If user provides `$ARGUMENTS`, pre-fill from that. This is the **raw/brief** content that will be enhanced in the next step.

5. **Content Style Instructions** - Ask the user for custom guidelines on how to rewrite/enhance the description (free text). Examples:

   • "use checkboxes for action items"
   • "use simple english"
   • "no emojis"
   • "add acceptance criteria section"
   • "keep it concise"
   • "use bullet points"

   This is a single free-text field where the user writes their style preferences.

Step 4: Enhance the description

The raw description from Step 3 is just a brief/rough input. Before creating the issue, **rewrite and enhance** the description following the user's content style instructions.

• Use the raw description as the source material
• Apply all the style guidelines the user provided
• Produce a well-structured, clear, professional GitHub issue body
• Do NOT ask the user for approval of the rewritten content -- just apply the instructions and proceed

Step 5: Ask for metadata

If a project was selected in Step 2, fetch the project's fields:

gh project field-list  --owner  --format json

Then ask the user to set:

1. Status - Show the available status options from the project's SingleSelect fields (e.g.