teamcraft-glgd:create-issue

---
name: teamcraft-glgd:create-issue
description: Create a single well-formed GitLab 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__gitlab__get_project
  - mcp__gitlab__list_projects
  - mcp__gitlab__list_milestones
  - mcp__gitlab__list_labels
  - mcp__gitlab__create_issue
  - mcp__google-drive__list_accounts
  - mcp__google-drive__search_files
  - mcp__google-drive__download_file
---

## Goal

Create one well-formed GitLab 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__gitlab__list_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 namespace string. Confirm once identified.

## Resolve Drive Account

Call `mcp__google-drive__list_accounts` before any other Drive operation:
- **No accounts** — Drive is not configured for this user. Tell them and skip Drive operations.
- **One account** — Use it. Pass `account_email` explicitly on every Drive tool call this session.
- **Multiple accounts** — Present the list, ask which account to use for this session. Pass that `account_email` on every Drive tool call.

If any Drive call returns a permission error, surface it: the active account may not have access to that file or folder. Offer to try another account if one is available.

If a Drive file operation fails with a path error, read the error message to identify a valid accessible host path and retry with it.

## Load Context

Ask the user if they can point at the tech decisions and conventions documents in Google Drive. If they can, use `mcp__google-drive__download_file` to load them directly. If they cannot, ask whether to search Drive. 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, bug, or chore. Ask if not clear from the description.

## 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 GitLab. If open milestones exist, offer to assign it to one. Report the IID and URL.

## PRD Integrity Check

After creating the issue, assess whether it represents a capability or requirement not currently reflected in the PRD. If it does — a new feature, a constraint discovered in implementation, a stakeholder request that extends original scope — flag it explicitly:

> "This issue adds capability X that is not in the current PRD. If this reflects a real change in scope, the PRD should be updated so all agents and team members work from accurate requirements. Would you like to update it now?"

If the user says yes, ask them to point at the PRD in Drive and update the relevant section. One atomic action — the issue and the PRD stay in sync at the moment scope changes, not weeks later.