skills.rest
masta-g3
masta-g3COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ticket-init

Parse natural language requests and append structured tickets to features.yaml.

1|Updated Jul 25, 2025
Search Tags:#automation#planning#epics#yaml#ticket#project-management#features.yaml
One-click install
npx skills add https://github.com/masta-g3/rules --skill ticket-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-init
Source: https://github.com/masta-g3/rules/tree/main/skills/ticket-init
Command: npx skills add https://github.com/masta-g3/rules --skill ticket-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert natural language requests into structured tickets and append them to features.yaml, simplifying backlog creation and epic alignment.

Core Features & Use Cases

  • Parse one or more user requests and generate tickets with id, epic, status, title, description, steps, and priority, then append to features.yaml.
  • Validate epic references, assign a sequential id, and record metadata like created_at, discovered_from, and plan_file for traceability.
  • Support both single-ticket and multi-ticket workflows, preserving independence between entries and enabling easy planning.

Quick Start

Register a new ticket for the "Improve onboarding" epic into features.yaml.

Frequently Asked Questions about ticket-init

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

FAQPage Schema
How do I create backlog tickets from natural language for project planning?▼

You can create backlog tickets from natural language by parsing user requests to generate structured entries with id, epic, status, title, description, steps, and priority, then appending them directly to features.yaml.

How do I append multiple feature tickets to features.yaml at once?▼

Appending multiple feature tickets to features.yaml is supported through multi-ticket workflows that parse several natural language requests simultaneously while preserving independence between each entry and maintaining proper created_at timestamps.

Can I associate new tickets with existing epics in YAML format?▼

Yes, associating new tickets with existing epics in YAML format is supported through epic reference validation during ticket creation, ensuring each generated ticket is properly linked to its parent epic in features.yaml.

What metadata is included when generating tickets in features.yaml?▼

Generating tickets in features.yaml includes metadata such as sequential id assignments, created_at timestamps, discovered_from, and plan_file for full traceability, alongside standard fields like title, description, steps, and priority.

Does ticket-init require any helper scripts to manage YAML project structures?▼

Yes, managing YAML project structures requires the features_yaml.sh helper script to properly format and append new ticket entries into features.yaml while maintaining correct YAML structure and validation.

What is the best way to automate backlog management from text requests?▼

Automating backlog management from text requests is best handled by converting natural language into structured YAML tickets with validated epic associations, sequential IDs, and traceability metadata for streamlined project planning.

Related Skills

Explore More Product & Management Skills→
masta-g3masta-g3
1

next-feature

Select the next feature to implement from features.yaml using priority rules.

Community
Intermediate
robotics-playgroundrobotics-playground

bmad-sprint-planning

Parse epic files to generate a complete sprint-status.yaml.

Official
Intermediate
MarkusonMarkuson

bmad-sprint-planning

Parse epic and story markdown to generate sprint-status.yaml tracking files.

Community
Advanced
DMT123DMT123

plugin-settings

Manage per-project plugin configurations using .claude/plugin-name.local.md files with YAML frontmatter.

Community
Intermediate