ilia f8ff2d3a55 feat(tts): Evaluate TTS options and select Piper
This commit completes the evaluation of Text-to-Speech (TTS) options
as described in TICKET-013.

- Creates a detailed  document comparing Piper,
  Mimic 3, and Coqui TTS.
- Recommends Piper for initial development due to its performance and
  low resource usage.
- Updates  to reflect the decision and points to the
  new evaluation document.
- Moves TICKET-013 to the 'done' column.
2026-01-05 20:33:53 -05:00
..

Kanban Tickets

This directory contains all project tickets organized by their kanban status.

Directory Structure

  • backlog/: Future work items that are planned but not yet ready to start
  • todo/: Items that are ready to be worked on
  • in-progress/: Items currently being actively developed
  • review/: Items that are complete but awaiting review, testing, or approval
  • done/: Completed items (archived for reference)

Ticket Naming Convention

Tickets should be named using the format:

[TICKET-ID]_[short-description].md

Example: TICKET-001_setup-project-structure.md

Workflow

  1. Create: New tickets start in backlog/ or todo/ depending on readiness
  2. Start Work: Move ticket from todo/ to in-progress/ when starting
  3. Complete: Move ticket from in-progress/ to review/ when implementation is done
  4. Approve: Move ticket from review/ to done/ when approved/merged

Using with Vibe Kanban

  1. Create tickets in this directory structure
  2. Import or reference these tickets in your Vibe Kanban board
  3. Keep ticket files in sync with kanban board status
  4. Use ticket IDs to reference in commits and PRs

Template

Use TICKET_TEMPLATE.md when creating new tickets to ensure consistency.