potatocreate-ticket

name: potato:create-ticket description: "Use this skill to create a new ticket in the current project. Use this to convert a brainstorm into a formal ticket for tracking development work."

Creating Tickets

Use the create_ticket MCP tool to create tickets. Tickets are the primary unit of work tracking in Potato Cannon.

The Rule

When work needs tracking, create a ticket. No mental tracking. No "I'll remember this."

Work without a ticket = work that gets lost, duplicated, or forgotten.

Parameters

Basic Usage

create_ticket({
  title: "Add user authentication",
});

With Description

Include a description. Tickets without descriptions become "what was this for?" mysteries.

create_ticket({
  title: "Add user authentication",
  description: `## Overview

Implement user authentication using JWT tokens.

## Requirements

- Login endpoint with email/password
- JWT token generation and validation
- Protected route middleware
- Logout endpoint

## Acceptance Criteria

- Users can log in with valid credentials
- Invalid credentials return appropriate errors
- Protected routes reject unauthenticated requests`,
});

From Brainstorm

When converting a brainstorm into a ticket, you MUST include the brainstormId. This maintains traceability.

create_ticket({
  title: "Implement dashboard analytics",
  description: "Analytics dashboard as discussed in brainstorm session.",
  brainstormId: "brain_abc123",
});

Brainstorm without ticket link = context lost forever.

When to Create Tickets

Red Flags - Create a Ticket Instead

These thoughts mean you need a ticket:

• "I'll just quickly do this"
• "This is too small to track"
• "I'll remember what this was about"
• "Let me just start coding"

All of these lead to lost work, forgotten context, or duplicated effort.

Ticket vs Task

Create a ticket for the overall feature. Break into tasks during Build phase. Never create tasks without a parent ticket.

Rationalization Table