ticket

Generate technical tickets from project objectives by analyzing the codebase.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/wolfbela/claude-skill --skill ticket-wolfbela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticket
Source: https://github.com/wolfbela/claude-skill/tree/main/weshake/skills/ticket
Command: npx skills add https://github.com/wolfbela/claude-skill --skill ticket-wolfbela

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, and includes scripts (resource) components.

What problem does it solve?

An objective-driven approach to ticket creation that analyzes a codebase to generate well-scoped, consistent technical tickets, reducing manual planning time and ensuring thorough coverage.

Core Features & Use Cases

  • Generate one ticket per bullet point objective or a single ticket for plain-text objectives.
  • Analyze repository structure to surface relevant files, endpoints, and validation needs for each ticket.
  • Provide a ready-to-submit ticket payload via the task manager script with clear testing guidance.

Quick Start

Tell it a clear objective and it will generate one or more tickets with structured details and testing guidance.

Frequently Asked Questions about ticket

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

FAQPage Schema
How do I generate technical tickets from project objectives automatically?

You can generate one ticket per bullet point in a list objective or a single ticket for a plain-text objective, with the tool analyzing your codebase to structure the appropriate number of tickets.

Can I generate issue-tracking tickets for both frontend and backend codebases?

Yes, you can generate issue-tracking tickets for both frontend and backend contexts, with the tool validating feasibility by exploring relevant files and endpoints across the codebase.

Do I need curl and jq installed to automate ticket creation from a codebase?

Yes, curl and jq are required dependencies to run the task manager script that processes repository data and stores the generated ticket payloads.

What is the best way to ensure generated development tickets have realistic scope?

The best way to ensure realistic scope is to use an objective-driven generator that analyzes your repository structure to surface relevant files, endpoints, and validation needs before creating the ticket.

How are the generated technical tickets stored and submitted to the task manager?

Generated technical tickets are stored and submitted via the task manager script, which produces a ready-to-submit payload containing structured details and clear testing guidance.