planning-tickets

Generate structured GitHub issues with EARS requirements and dependency graphs.

4|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/tomada1114/tomada-claude-plugins --skill planning-tickets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning-tickets
Source: https://github.com/tomada1114/tomada-claude-plugins/tree/main/agile-tools/skills/planning-tickets
Command: npx skills add https://github.com/tomada1114/tomada-claude-plugins --skill planning-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn requirements into actionable GitHub Issues using agile/scrum practices; it guides ticket decomposition, parallel work identification, dependency mapping, and worktree planning.

Core Features & Use Cases

  • Automate ticket breakdown from requirements into independent issues
  • Plan sprints with parallel workstreams
  • Suggest git worktree strategies to enable parallel development
  • Provide EARS-formatted requirements templates and examples

Quick Start

Use this skill by submitting a project idea or requirements statement; the skill will generate an implementation plan that includes foundation tickets, parallel tickets with worktree suggestions, and integration tickets.

Frequently Asked Questions about planning-tickets

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

FAQPage Schema
How do I break down GitHub issues into parallel workstreams for agile sprints?

Decompose requirements into independent GitHub issues mapped to parallel workstreams. This Skill analyzes your requirements, generates EARS-formatted acceptance criteria and dependency graphs, then suggests git worktree strategies to enable teams to work on multiple tickets simultaneously without blocking.

What's the best way to plan dependencies between GitHub issues?

Map explicit dependencies across tickets using dependency graphs. This Skill translates requirements into structured issues with boundary conditions and concrete examples, showing which tickets must complete first and which can run in parallel to optimize sprint planning.

Can I use git worktree to organize parallel development on multiple GitHub issues?

Yes. This Skill recommends worktree strategies tailored to your ticket decomposition plan, enabling developers to switch between independent issues without context switching, improving throughput on parallel workstreams.

How do I automate ticket breakdown from a requirements statement?

Submit your project idea or requirements to this Skill. It generates foundation tickets, parallel tickets with worktree guidance, and integration tickets with EARS-formatted requirements, acceptance criteria, and an explicit dependency graph for deterministic implementation.

What format should requirements follow for GitHub issue planning?

EARS-formatted requirements provide structured clarity for issue decomposition. This Skill applies EARS templates alongside acceptance criteria, boundary conditions, and concrete examples to ensure each GitHub issue is actionable and dependencies are explicit.

When should I map dependencies before creating GitHub issues?

Map dependencies upfront during sprint planning to identify parallel work and avoid bottlenecks. This Skill generates a complete dependency graph before ticket creation, ensuring teams can execute multiple issues concurrently and integration points are clear.