teamcraft-jcg:create-issue

---
name: teamcraft-jcg:create-issue
description: Create a single well-formed Jira issue at any time — bugs found in production, features requested by stakeholders, technical debt noticed during development, chores that need doing. Follows the same issue standards as plan-sprint, always. Works in Claude Cowork and Claude Code.
argument-hint: "[brief description of the issue]"
disable-model-invocation: true
user-invocable: true
allowed-tools:
  - mcp__sooperset-mcp-atlassian__jira_get_all_projects
  - mcp__sooperset-mcp-atlassian__jira_create_issue
  - mcp__sooperset-mcp-atlassian__jira_search_fields
  - mcp__sooperset-mcp-atlassian__confluence_search
  - mcp__sooperset-mcp-atlassian__confluence_get_page
---

## Goal

Create one well-formed Jira issue that gives a developer everything they need to pick it up cold. The same standards apply regardless of when or why the issue is created. One issue. Explicit confirmation. No exceptions.

## Identify the Project

Use `mcp__sooperset-mcp-atlassian__jira_get_all_projects` to see what is visible, surface the results, and ask the user which project this issue belongs to. Never ask the user to supply a project key string. Confirm once identified. Record the Jira project key.

## Load Context

Ask the user if they can point at the tech decisions and conventions documents in Confluence. If they can point at a page by URL or ID, use `mcp__sooperset-mcp-atlassian__confluence_get_page` directly. If they cannot, use `mcp__sooperset-mcp-atlassian__confluence_search` to find relevant pages. If page IDs are available from `.teamcraft/project.md`, use them directly. These documents inform the technical guidance section of the issue. If nothing is available, proceed without — the user's description carries sufficient context.

## Understand the Issue

Use `$ARGUMENTS` as the starting point if provided. Determine issue type — feature (Story), bug, task, or chore. Ask if not clear from the description.

Standard Jira issue types are Story, Bug, Task, Epic, and Subtask — the `mcp__sooperset-mcp-atlassian__jira_create_issue` tool accepts the type as a string. If the user describes a non-standard type or you need to discover custom fields, use `mcp__sooperset-mcp-atlassian__jira_search_fields` to find available fields by keyword.

## Draft and Confirm

Before drafting, read the reference file matching the issue type — `references/example-feature-issue.md`, `references/example-bug-issue.md`, or `references/example-chore-issue.md`. These define the required structure. Every issue must include all sections from the reference: Background & Goal, Acceptance Criteria, Technical Guidance, and Testing Requirements (for features and bugs) or Verification (for chores). An issue missing any of these sections is incomplete.

Show the draft. Get explicit confirmation before creating. Never create without approval.

## Create

Create the issue in Jira using `mcp__sooperset-mcp-atlassian__jira_create_issue`. Issues are created in the backlog — sprint assignment is handled by the PM during sprint planning. Report the issue key (e.g., PROJ-42) and URL.