### Tracking Spec Kitty tasks with tix
This project runs Spec Kitty (detected via `.kittify/`). Use tix to track its task issues:
- Filing a Spec Kitty task/work package → `tix create --title "<wp title>" --labels spec-kitty`
- Opening an issue → `tix list --status "todo"`
- Associating work with a project → `tix project add <id> <sel>…`; `tix list
--project <id>` lists a project's issues
- Recording an issue's health → `tix health set <n> --state <state> --rationale "<why>"`
(states: unknown, on_track, needs_attention, at_risk; `tix health show <n>` reads one back)
- Add the specification / plan of the concrete task in the issue markdown body.
- Marking a task done → `tix move <number> done` (interactive) or
`tix move <number> done --commit <hash>` (non-interactive)
- Commenting on a task issue → `tix edit <number>` (body/comment section is plain markdown)
- **REQUIRED — always use `tix mcp` to create and move tix issues** while
tracking Spec Kitty tasks. The MCP server is wired into this repo
(`opencode.jsonc`), so in opencode call the `tix_*` tools directly:
`create_issue` to file a new task issue, `move_issue` to advance it (moving
to `done` records the commit via the `commit` argument), and the read tools
(`list_issues`, `get_issue`, `board_status`, `search_issues`) to inspect the
board. Do NOT hand-edit issue files or drive status changes through the CLI
prompts. See `docs/mcp.md`.
- **REQUIRED — mirror every Spec Kitty task as a tix issue.** For each finished
mission/work package, create tix issues replicating: (1) every spec-kitty
subtask (T0xx) as its own issue, and (2) every review finding / follow-up
item. All get `--labels spec-kitty`. Add the task spec/plan in the issue body.
Mark matching issues `done --commit <hash>` when the lane/commit lands.