Implementation Roadmap

The roadmap is phased so every step leaves a usable command behind. No inert infrastructure, no TUI-only capability.

Current command check

spotuify --help
spotuify doctor
scripts/cargo-test -p spotuify-cli --tests

Phases

Phase	Goal	Verification
0	Stabilize current app	spotuify doctor, spotuify search, playback smoke
1	CLI parity	status/devices/search/playback/queue/playlists/library commands
2	Daemon and IPC	CLI/TUI use socket, daemon survives TUI exit
3	SQLite and Tantivy	local search works without waiting on Spotify
4	TUI redesign	player-first UI, hint bar, palette, diagnostics
5	Agent playlists	plan, resolve, dry-run, commit
6	Sync hardening	rate limits, freshness, snapshot gates
7	Workspace split	real crate boundaries
8	MCP server	tools/list, tool routing, live resources
9	Embedded librespot	one auth flow, local playback backend
10	Analytics	derived listens, top-N, habits, exports
11	Cross-platform	launchd, systemd user, Task Scheduler
12	Operation log and undo	recorded mutations with reversal plans
13	Spec compliance and QoL	reload, reconnect, overrides, bug reports
14	System integration	media keys, notifications, hooks
15	Cover art	inline art plus fallbacks
16	Lyrics	synced lyrics and offset tuning
17	Audio visualization	FFT spectrum via sink tap or loopback

Do not skip the CLI

Every new user-visible capability needs a real command:

spotuify <capability> --format json

If a capability has only a TUI button, it is incomplete.

See Also

• Architecture
• CLI Reference
• Research Notes