ticket-craft

Create self-contained software tickets with acceptance criteria and verification commands.

Updated Jun 19, 2026
One-click install
npx skills add https://github.com/lciacci/tessera --skill ticket-craft-lciacci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket-craft
Source: https://github.com/lciacci/tessera/tree/main/skills/ticket-craft
Command: npx skills add https://github.com/lciacci/tessera --skill ticket-craft-lciacci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ticket Craft turns incomplete or ambiguous software requirements into self-contained tickets that Claude Code and other AI agents can execute without repeated clarification.

Core Features & Use Cases

  • AI-Ready Ticket Writing: Create detailed feature, bug, tech debt, and epic tickets with explicit context, constraints, dependencies, and verification steps.
  • Structured Acceptance Criteria: Apply INVEST+C principles, Given-When-Then scenarios, test commands, and definitions of ready and done.
  • Use Case: When a team needs to add an API feature, use this Skill to produce a ticket that identifies relevant files, implementation patterns, API contracts, database changes, constraints, and exact validation commands.

Quick Start

Use the ticket-craft skill to create a Claude Code-ready feature ticket for the requested software change.

Frequently Asked Questions about ticket-craft

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Jira tickets that AI coding agents can execute without clarification?

To write Jira tickets for AI coding agents, you must include explicit file references, implementation patterns, acceptance criteria, constraints, dependencies, and exact verification commands. This ensures the software requirements are self-contained and executable.

What is the best way to break down an epic into actionable AI-ready tickets?

Breaking down an epic into AI-ready tickets involves applying INVEST+C principles and Given-When-Then scenarios. This process translates large feature requests into self-contained software tickets with specific file references and exact validation commands.

How do I add acceptance criteria and verification steps for technical debt tickets?

Adding acceptance criteria for technical debt tickets requires applying INVEST+C principles, Given-When-Then scenarios, test commands, and definitions of ready and done. This ensures the software requirements have exact validation commands for verification.

Does ticket-craft work with Linear and GitHub Issues for agile planning?

Ticket-craft supports agile planning across Jira, Asana, Linear, and GitHub Issues. It transforms vague work into structured software tickets with explicit context, constraints, dependencies, and verification steps for AI agent execution.

Why do my feature requests require repeated clarification from AI coding agents?

Feature requests require repeated clarification when they lack explicit context, API contracts, database changes, and exact verification commands. Structuring tickets as self-contained software requirements with implementation patterns resolves this ambiguity.