create-tickets

Converts natural-language proposals into investigation-backed TCK ticket files.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill create-tickets-ttnhan18062000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-tickets
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/.agents/skills/create-tickets
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill create-tickets-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing well-scoped engineering tickets from a rough proposal requires manual codebase investigation to find real file paths, existing tests, and acceptance criteria. This Skill automates that investigation and produces ready-to-implement ticket files. ## Core Features & Use Cases - Proposal Comprehension: Parses any natural-language markdown proposal into discrete concerns without requiring the author to supply file paths or acceptance criteria. - Multi-Step Investigation: Searches knowledge graphs, doc registries, prior ticket history, source code, and existing tests to derive concrete, testable acceptance criteria per concern. - Structured Ticket Writing: Generates TCK-YYYYMMDD-<SHORT-SCOPE>.md files with deduplication, tag-registry validation, dependency sequencing via SEQUENCE.md, and optional linking to an epic ticket. - Use Case: A product manager writes a feature proposal in docs/plans/proposal.md; run the skill to produce a folder of investigation-backed tickets, then hand them to /implement-epic for implementation. ## Quick Start Ask the agent to run create-tickets with source pointing at your proposal markdown file, for example: create tickets from docs/plans/proposal.md.

Frequently Asked Questions about create-tickets

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

FAQPage Schema
How do I create tickets from a proposal document?

Run the skill with source=<path to your proposal markdown>, for example /create-tickets source=docs/plans/proposal.md. The workflow comprehends the proposal, investigates the codebase, and writes TCK-*.md ticket files to an output folder.

How does the ticket investigation phase find file paths and acceptance criteria?

Investigation runs in a fixed order: semantic doc search and graphify queries first, then the knowledge graph report, docs/REGISTRY.yaml, prior ticket history in working_log.csv, code files, and existing tests. Acceptance criteria are derived from code behavior, doc constraints, and test patterns.

Do I need to provide file paths or acceptance criteria in my proposal?

No. The proposal can be written in any natural markdown format by anyone. The Investigate phase derives real file paths, doc constraints, and testable acceptance criteria from the codebase automatically.

What happens if a ticket uses an unregistered tag?

The tag-registry gate filters that task out of the write set and logs a blocked event. You register the tag with python3 tools/tag_registry.py add <tag> --category <cat> and re-run to pick up the skipped concern; the rest of the batch still writes.

Can I link created tickets to an existing epic?

Yes. Pass epic_id=<existing epic ticket ID> and the Link phase appends the new ticket IDs to the epic's Related Tickets section. If intra-batch dependencies are detected, a SEQUENCE.md is also written to enforce implementation order.