create-project

Optional environment variables:

• GHPM_TEMPLATE_PROJECT - Project number to use as template (e.g., "7")
• GHPM_TEMPLATE_OWNER - Owner of the template project (defaults to current repo owner)

<usage_examples>

With title argument:

/ghpm:create-project Q1 Roadmap

→ Creates project titled "Q1 Roadmap", links to current repo

Without title (prompts):

/ghpm:create-project

→ Prompts: "What should the project be called?" → Creates and links project

With template pre-configured:

export GHPM_TEMPLATE_PROJECT="7"
/ghpm:create-project Feature Development

→ Copies from template project #7, links to current repo

</usage_examples>

<operating_rules>

• Always prompt for project title if not provided via $ARGUMENTS
• Check for template projects before creating blank project
• Link the project to the current repository after creation
• Set GHPM_PROJECT to the new project title for use in subsequent commands
• Report the project URL so user can configure views manually if needed

</operating_rules>

<input_validation>

Validation Checks

Before proceeding, verify:

# 1. Verify gh CLI authentication
gh auth status || { echo "ERROR: Not authenticated. Run 'gh auth login'"; exit 1; }

# 2. Verify project scope
gh auth status 2>&1 | grep -q "project" || echo "WARNING: Token may not have 'project' scope. Run 'gh auth refresh -s project' if project creation fails."

# 3. Verify in git repository
git rev-parse --git-dir > /dev/null 2>&1 || { echo "ERROR: Not in a git repository"; exit 1; }

# 4. Verify GitHub remote exists
gh repo view --json nameWithOwner -q .nameWithOwner || { echo "ERROR: No GitHub remote found"; exit 1; }

</input_validation>