create-tickets

To convert architecture documents into sequenced sprint tickets, feed architecture-update.md and usecases.md into the ticket generation process. It outputs numbered tickets with explicit dependencies, descriptions, and acceptance criteria for execution tracking.

Dependency-aware ticket sequencing orders implementation tickets so foundation work precedes features. It captures inter-ticket dependencies within sprint planning, ensuring architecture tasks are executed in the correct order for smooth development.

You generate actionable tickets from use cases by processing usecases.md alongside architecture updates. The output consists of discrete ticket files featuring unique IDs, statuses, use-case references, descriptions, and acceptance criteria for project management.

Yes, the ticketing process requires architecture-update.md and usecases.md as specific input file formats. These markdown documents provide the necessary sprint architecture and use case context to produce properly sequenced, dependency-aware tickets.

Generated sprint tickets include frontmatter metadata containing an id, title, status, use-cases, and depends-on fields. The ticket body also contains a description and acceptance criteria to ensure full traceability and clear implementation guidance.

Yes, you can trace sprint tickets back to original architecture documents. The system propagates references to related issues and documentation, ensuring full traceability from each generated ticket back to its source use cases and architecture updates.