ticket

Plan and create Markdown tickets with standardized filenames and templates.

Updated Sep 12, 2021
One-click install
npx skills add https://github.com/cerico/macfair --skill ticket-cerico
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/cerico/macfair/tree/main/files/claude/skills/ticket
Command: npx skills add https://github.com/cerico/macfair --skill ticket-cerico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of planning and creating actionable tickets for Ralph to work on later, helping teams turn ideas into concrete tasks that can be tracked and executed.

Core Features & Use Cases

  • Interactive ticket planning: Work with users to elicit requirements, references, and acceptance criteria.
  • Ticket generation: Create self-contained Markdown tickets with standardized filenames in a ready-to-use directory.
  • Backlog grooming & workflow: Build a backlog of well-scoped tickets that Ralph can pick up and complete.

Quick Start

Plan and create your first ticket by following these steps:

  • Create the target directory if needed: mkdir -p tmp/tickets/done
  • Gather requirements from the user: What needs to be done? Any reference numbers? Any files or areas affected? Acceptance criteria?
  • Create a ticket filename: {REFERENCE}-{short-description}.md (e.g., CEL-001-add-logout-button.md)
  • Use the ticket template to fill in Title, Context, Files, and Acceptance Criteria
  • Keep tickets atomic and actionable; Ralph handles one ticket at a time
  • After creation, check pending work with ralph status or start work with ralph run

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I create actionable markdown tickets for backlog grooming?

To create actionable markdown tickets for backlog grooming, this Skill interactively elicits requirements and acceptance criteria, then generates standardized markdown files in tmp/tickets with structured titles, context, and filenames. It ensures tasks are atomic and ready for execution.

What is the standardized ticket format for breaking down features into discrete tasks?

The standardized ticket format for discrete tasks includes a specific filename convention like {REFERENCE}-{short-description}.md, along with a template containing Title, Context, Files, and Acceptance Criteria sections to ensure clear scoping.

Can I automate markdown ticket creation for my project workflow?

Yes, you can automate markdown ticket creation within your project workflow. This Skill automatically writes self-contained tickets to a ready-to-use directory using a consistent template and filename structure derived from interactive planning.

Does this ticket planning tool enforce consistent filenames for tracking work?

Yes, this ticket planning tool enforces consistent filenames for tracking work. It applies a standardized naming convention using reference numbers and short descriptions to ensure backlog items are easily identifiable and organized.

What's the best way to prepare my directory before planning tickets?

The best way to prepare your directory for planning tickets is to run mkdir -p tmp/tickets/done. This setup ensures the generated markdown files have a proper destination folder for pending and completed work tracking.

What are the limitations of interactive ticket planning for backlog management?

A limitation of this interactive ticket planning approach is that tickets must remain atomic; the system handles one ticket at a time. It focuses solely on markdown generation and does not execute the described tasks automatically.