What problem does it solve?
Converts approved Feature Docs (PRDs) into clear, testable engineering tickets so product managers and engineers avoid manual ticket writing, missed acceptance criteria, and hidden dependencies.
Core Features & Use Cases
- Structured ticket generation: Breaks a Feature Doc into component-specific tickets with titles, acceptance criteria sourced from Section 5 use cases, technical notes, and dependencies.
- Direct or fallback delivery: Creates issues directly in Linear or Jira when MCPs are configured, or generates copy-paste formatted ticket text when they are not available.
- Planning and estimation: Adds T-shirt sizing or story points, groups work into epics/sprints, and produces a dependency summary and sprint assignment recommendations.
- Use case: PM runs this immediately after Feature Doc approval to produce a parent epic, child tickets with estimates, and a dependency graph for engineering handoff.
Quick Start
Create tickets from the approved Feature Doc by specifying the source document, target system (Linear, Jira, or text), project/team, ticket type, and priority.