create-tickets

To convert sprint architecture into sequenced tickets, provide architecture-update.md and usecases.md files. The system parses them to generate numbered ticket files with dependencies, acceptance criteria, and implementation plans in the sprint's tickets directory.

Generating agile tickets with dependencies requires parsing architecture and use-case documents. The tool propagates references, ensures complete traceability, and orders foundational work before dependent features to prevent circular dependencies.

Yes, architecture-update.md and usecases.md files are required inputs to generate sprint tickets. The system reads these documents to extract features, map dependencies, and produce actionable ticket files with frontmatter fields for tracking.

You can automate sprint planning by feeding architecture and use-case documents into the ticket generation process. It outputs ordered ticket files containing descriptions, acceptance criteria, and implementation plans to guide discrete development sessions.

Ticket traceability works by propagating references across sprint documentation. Each generated ticket includes frontmatter fields linking use-cases and depends-on IDs, ensuring complete coverage from architecture updates through to implementation plans.