ticketize

Break feature briefs into vertical tracer-bullet tickets with dependencies.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Suniljit/personal-toolkit --skill ticketize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ticketize
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/ticketize
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill ticketize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break feature briefs into independently-grabbable vertical slices by producing tracer-bullet tickets that map end-to-end across all integration layers, enabling incremental delivery and clear visibility of work items.

Core Features & Use Cases

  • Draft vertical slices (tracer bullets) that traverse all integration layers end-to-end.
  • Create many small, reviewable tickets that can be merged via small PRs and tracked against the feature brief.
  • Manage dependencies and blockers with a clear execution order aligned to FRs and user stories for traceability.

Quick Start

Ask the user for the feature brief location and begin drafting tracer-bullet tickets.

Frequently Asked Questions about ticketize

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

FAQPage Schema
How do I break a feature brief into vertical slices for incremental delivery?

Breaking a feature brief into vertical slices involves creating tracer-bullet tickets that map end-to-end across all integration layers, enabling incremental delivery and clear visibility of independently grabbable work items.

What are tracer bullets in agile planning and how do they work for ticketing?

Tracer bullets in agile ticketing are end-to-end vertical slices that traverse all integration layers, producing many small, reviewable tickets that can be merged via small PRs and tracked against the feature brief.

Can I prioritize tickets by functional requirements and user stories from a feature brief?

Yes, you can prioritize tickets by functional requirements and user stories from a feature brief. The process enforces deterministic ticket creation and alignment to ensure traceability and manage dependencies with a clear execution order.

What's the best way to manage dependencies and blockers across integration layers?

The best way to manage dependencies and blockers across integration layers is to produce a stepwise plan with clear execution order, aligning tickets to functional requirements and user stories for full traceability against the feature brief.

Does this approach to ticket creation work for small PRs and quick reviews?

Yes, this ticket creation approach works for small PRs and quick reviews by generating many small, reviewable tickets that can be merged incrementally and tracked directly against the feature brief.

When do I need to use tracer bullets for requirements tracking?

You need to use tracer bullets for requirements tracking when you must break feature briefs into independent vertical slices with deterministic ticket creation, prioritization by functional requirements, and clear alignment for traceability.