create-tickets

Name: create-tickets
Availability: InStock
Author: Busboom-Foo

Convert architecture and use case documents into dependency-aware sprint tickets.

Updated Apr 3, 2026

Search Tags:#automation #architecture #dependencies #project-management #sprint-planning #ticketing

Ready to run

npx skills add https://github.com/Busboom-Foo/meetupfu --skill create-tickets-busboom-foo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-tickets
Source: https://github.com/Busboom-Foo/meetupfu/tree/main/.claude/skills/create-tickets
Command: npx skills add https://github.com/Busboom-Foo/meetupfu --skill create-tickets-busboom-foo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks a sprint's architecture document into sequenced, numbered implementation tickets with explicit dependencies to guide execution and tracking.

Core Features & Use Cases

Ticket generation: Converts architecture and use cases into discrete, actionable tickets with clear IDs and statuses.
Dependency-aware sequencing: Orders tickets so foundation work precedes features and captures inter-ticket dependencies.
Traceability: Propagates references to related issues and documentation, ensuring full traceability.

Quick Start

Feed the sprint's architecture-update.md and usecases.md into the ticket creation process to produce tickets in tickets/NNN-slug.md with frontmatter, descriptions, and acceptance criteria.

Frequently Asked Questions about create-tickets

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

FAQPage Schema

How do I convert architecture documents into sequenced sprint tickets?▼

To convert architecture documents into sequenced sprint tickets, feed architecture-update.md and usecases.md into the ticket generation process. It outputs numbered tickets with explicit dependencies, descriptions, and acceptance criteria for execution tracking.

What is dependency-aware ticket sequencing in sprint planning?▼

Dependency-aware ticket sequencing orders implementation tickets so foundation work precedes features. It captures inter-ticket dependencies within sprint planning, ensuring architecture tasks are executed in the correct order for smooth development.

How do I generate actionable tickets from use cases for project management?▼

You generate actionable tickets from use cases by processing usecases.md alongside architecture updates. The output consists of discrete ticket files featuring unique IDs, statuses, use-case references, descriptions, and acceptance criteria for project management.

Does this ticketing process require specific input file formats?▼

Yes, the ticketing process requires architecture-update.md and usecases.md as specific input file formats. These markdown documents provide the necessary sprint architecture and use case context to produce properly sequenced, dependency-aware tickets.

What metadata is included in generated sprint tickets?▼

Generated sprint tickets include frontmatter metadata containing an id, title, status, use-cases, and depends-on fields. The ticket body also contains a description and acceptance criteria to ensure full traceability and clear implementation guidance.

Can I trace sprint tickets back to original architecture documents?▼

Yes, you can trace sprint tickets back to original architecture documents. The system propagates references to related issues and documentation, ensuring full traceability from each generated ticket back to its source use cases and architecture updates.