Use when hardening Ion's user experience by driving the ion CLI end-to-end against a real project and improving what feels rough — i.e. "dogfood ion on <project>", "use ion in X and fix the UX gaps", "is ion actually pleasant to use", "does ion guide the agent to the next step", or any shakedown of the CLI from a user's seat. Dogfooding judges three things at once: (1) human terminal UX — is plain (non-JSON) output friendly and readable; (2) progressive prompting — does every command's output (human text AND the --json envelope) make the next step obvious so a user or agent never stalls; (3) workflow ergonomics — does a real goal take too many commands, calling for a new or consolidated command rather than another hint. Covers driving the full skill lifecycle on a scratch repo and an established one, logging each rough edge, and FIXING the CLI (next-step hints, richer action_required envelopes, friendlier output, new/merged commands) with a failing-test-first discipline using the scenario crate + integration

2026-07-1874

name

Roger-luo/Ion

2026-03-2974