issue

Create Issue: $ARGUMENTS

Skill-driven issue creation. Follows the Explore > Plan > Code > Verify loop with issue-crafting skill knowledge.

Required Skills

• issue-crafting — solution-agnostic issues, duplicate detection, label discovery

Phase 1: EXPLORE

Gather context before formulating the issue.

# Output: `###`-headed sections + KEY=value per
# `references/command-output-format.md`.

echo "### Repo Context"
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner' 2>/dev/null)
if [ -z "$REPO" ]; then
  echo "STATE=unavailable"
  echo "ERROR=cannot resolve repo (gh auth or non-repo CWD?)"
else
  echo "STATE=ok"
  echo "REPO=$REPO"
fi

echo ""
echo "### Git State"
echo "BRANCH=$(git branch --show-current 2>/dev/null)"
UNCOMMITTED_COUNT=$(git status --porcelain 2>/dev/null | wc -l | tr -d ' ')
echo "UNCOMMITTED_COUNT=$UNCOMMITTED_COUNT"
[ "$UNCOMMITTED_COUNT" != "0" ] && git status --short 2>/dev/null | head -20 | sed 's/^/UNCOMMITTED_LINE=/'

true

Branch context extraction: If on a feature branch matching feature/issue-{N}-* or fix/issue-{N}-*, extract the issue number — the new issue may be related.

Requirements gathering from $ARGUMENTS:

If $ARGUMENTS provides a description, parse it for initial context. For each missing element, use the AskUserQuestion tool with contextual options:

1. Context: "What's the background/motivation for this issue?"
2. Current State: "What's happening now? What's the problem or gap?"
3. Objective: "What should be achieved? Describe the desired outcome."
4. Acceptance Criteria: "What observable behaviors prove this is complete?"

If $ARGUMENTS is empty, walk through all four elements interactively.

Iron law enforcement: If any gathered element contains file paths, function names, class names, or implementation details — rewrite it to describe outcomes instead. Example:

• Bad: "Add a reset_password method to UserController"
• Good: "Users can reset their password via email"