skills.rest
ganzinn
ganzinnCOMMUNITY
Explore all skills by this author →
GitHub

ticket-split

Generate PR-ready NN-*.md tickets and README from design hubs.

Updated Apr 19, 2026
Search Tags:#planning#docs#software-development#project-management#ticketing#ticket-split#design-hub
One-click install
npx skills add https://github.com/ganzinn/deja-word --skill ticket-split
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-split
Source: https://github.com/ganzinn/deja-word/tree/main/.claude/skills/ticket-split
Command: npx skills add https://github.com/ganzinn/deja-word --skill ticket-split

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the handoff from completed design work to implementation planning by automatically partitioning design hubs into PR-ready tickets under docs/plan and generating corresponding NN-*.md tickets.

Core Features & Use Cases

  • Generates a docs/plan/<機能名>/README.md from design hubs, outlining planned tickets and dependencies.
  • Creates individual NN-*.md ticket files for each planned task, including scope, dependencies, and acceptance criteria.
  • References the original design decisions with source citations to ensure traceability and alignment with planning standards.

Quick Start

Run the skill to generate a docs/plan/<機能名>/README.md and corresponding NN-*.md tickets from your design hubs.

Frequently Asked Questions about ticket-split

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

FAQPage Schema
How do I generate PR-ready tickets from a design hub?▼

You can convert design hubs into PR-ready ticket plans by running this Skill to automatically generate a docs/plan/<機能名>/README.md and corresponding NN-*.md ticket files. It partitions design decisions into scoped tickets with dependencies and acceptance criteria.

What is the best way to structure implementation tickets for software development planning?▼

The best way to structure implementation tickets is to generate a README outlining planned tickets and dependencies, alongside individual NN-*.md files. Each ticket defines scope, dependencies, and acceptance criteria with explicit source citations to original design decisions.

How does ticket generation handle traceability to original design decisions?▼

Traceability is maintained by embedding explicit source citations to original design decisions within each generated ticket file. This ensures every planned task under docs/plan/ aligns with the confirmed decision summaries from the design hub.

Do I need confirmed decision summaries to create project management tickets?▼

Yes, confirmed decision summaries in the design hub are required to create project management tickets. The Skill specifically identifies design hubs with confirmed summaries to generate scoped tickets and README files under docs/plan/.

Can I use this for breaking down project management documentation into individual task files?▼

Yes, you can use this for breaking down project management documentation into individual task files. It scopes the output to creating a README and individual NN-*.md ticket files, partitioning design hubs into actionable tasks with dependencies and acceptance criteria.

What limitations exist when partitioning design hubs into docs/plan directories?▼

A key limitation when partitioning design hubs into docs/plan directories is the strict requirement for confirmed decision summaries; without them, ticket generation cannot proceed. Output is also strictly scoped to README and NN-*.md files following plan hub conventions.

Related Skills

Explore More Software Engineering Skills→
jMertajMerta
130

ui-ux-pro-max

Search a UI/UX design knowledge base using BM25 ranking.

Community
Intermediate
AnastasiyaWAnastasiyaW
140

plan-to-tickets

Decompose project plans into Markdown tickets with acceptance criteria.

Community
Intermediate
ganzinnganzinn

ticket-implement

Automate ticket implementation workflows from plan hub through PR orchestration.

Community
Advanced
YeaChan05YeaChan05

spec

Define problem, scope, and acceptance criteria into a /plan artifact.

Community
Intermediate