cqs-planlisted

# Plan Generate an implementation plan by combining `cqs scout` output with a task-type template. ## Process 1. **Classify the task** into one of the templates below based on the description. 2. **Run scout**: `cqs scout "<task description>" --json -q` 3. **Run targeted lookups** from the template's checklist — scout alone misses structural touchpoints (clap structs, dispatch arms, skill files). 4. **Produce a plan** listing every file to change, what to change, and why. Be specific about struct fields, function signatures, and match arms. ## Arguments - `$ARGUMENTS` — task description (required) ## Templates ### Add/Replace a CLI Flag **When:** Adding a new flag, renaming a flag, changing a flag's type (bool → enum). **Checklist:** 1. `src/cli/mod.rs` — `Commands` enum variant. Add/modify `#[arg]` field. If enum-typed, define with `clap::ValueEnum`. 2. `src/cli/mod.rs` — `run_with()` match arm. Update destructuring and `cmd_<name>()` call. 3. `src/cli/commands/<name>.rs` — `cmd_<name>()` signature. Update branching logic. 4. `src/cli/commands/<name>.rs` — Display functions if the flag affects output format. 5. `src/store/*.rs` / `src/lib.rs` — Usually NO changes. Only if flag affects query behavior. 6. Tests: `tests/<name>_test.rs` — add case for new value. Update tests using old flag name. 7. `.claude/skills/cqs-<name>/SKILL.md` — update argument-hint and usage. 8. `README.md` — update examples if the command is featured. 9. Verify callers: `cqs callers cmd_<name>