spec-to-tickets

To break down a software spec into actionable tickets, you decompose gate specs into executable work items mapped to codified validation. This process validates spec assumptions against the codebase first, then produces ticket files with explicit dependencies and topological order.

The best way to map ticket dependencies for a roadmap is to generate ticket batches with explicit Deps wiring and topological ordering. This ensures each ticket follows a standard template, records files to touch, and maintains traceable dependencies for sequential implementation.

To ensure generated tickets align with project foundations, the decomposition process enforces a codified validation alignment. Each ticket explicitly records dependencies, files to touch, and test plans to guarantee cross-spec consistency and deterministic implementation planning.

You need to provide a spec_path pointing to your gate spec, which can reside within specs/, .claude/skills/, docs/, templates/, or code trees. The tool then generates the output tickets in the tickets/ directory following the _TEMPLATE.md format.

Yes, you can generate tickets from specs stored in docs and code trees by providing the spec_path. The tool operates across specs/, docs/, templates/, and code directories to produce structured ticket files with pre-flight checks and test plans.