1. Study what this product does today: skim the README, the docs, and the main user-facing surfaces, plus the existing `tickets/`
2. Think like a product manager and propose net-new features the product should have next
   - Net-new capabilities a user would want, not bugs, refactors, or chores
   - Skip anything an existing ticket already covers, and anything already built
   - Favour features that fit the product's direction and are worth building
3. Write each proposed feature as a new ticket under `tickets/`, following the ticket format
4. Show a short summary of what you proposed via `showMarkdown()`
