## Codex + td Workflow

### Session bootstrap (mandatory)
- At conversation start (or after `/clear`), run `td usage --new-session` once.
- For later reminders in the same conversation, run `td usage -q`.
- Do not start a second td session mid-task.

### Pick and track work
- Check active context with `td current`.
- If no focused issue is active, pick one with `td next` and begin with `td start <id>`.
- Log meaningful progress using `td log "<message>"`.

### New feature workspace (mandatory)
- When starting a new feature, start a fresh td workspace first.
- Use `tools/bin/td-feature-start "<feature-name>" <id...>`.
- If issue IDs are omitted, it tags the currently focused issue when available.
- Do not begin new-feature implementation outside a td workspace.

### Required completion flow
- Before stopping work, capture current state with `td handoff <id>`.
- Submit finished work with `td review <id>`.
- Do not use `td close` for completed work.
- Approvals are done by a different session via `td approve <id>`.

### Multi-issue work
- Use workspace mode when handling related issues:
  - `td ws start "<name>"`
  - `td ws tag <id1> <id2> ...`
  - `td ws log "<message>"`
  - `td ws handoff`

### Guardrails
- Keep td issue IDs in notes, logs, and handoffs.
- Prefer small, frequent `td log` updates over one large final update.
- If td state and local git state disagree, report both explicitly.