add-testslisted

# Add Tests Turn a coverage gap into `ready-for-agent` issues that `crew-afk` or `/solve-issue` can pick up directly — no special-casing needed on either downstream path. ## Process ### 1. Resolve the coverage and integration commands Use the same discovery/cache mechanism `crew-afk`/`solve-issue` already use: ```bash bash scripts/discover-commands.sh ``` This prints either a skip message (the cache already has both fields) or a discovery prompt — hand that prompt to a model, then persist its response: ```bash bash scripts/write-commands-cache.sh --response-file <path> ``` Then read the two fields this skill needs from `.coding-crew/dev-commands.json`, the same way `ensure-deps.sh` already reads `install`: ```bash grep -o '"coverage"[[:space:]]*:[[:space:]]*"[^"]*"' .coding-crew/dev-commands.json grep -o '"integration"[[:space:]]*:[[:space:]]*"[^"]*"' .coding-crew/dev-commands.json ``` **If `coverage` resolves to `null`** (a model already looked and confirmed no coverage command exists), tell the user plainly and stop: > "This project has no coverage command configured, so I can't find coverage gaps. Add one to > `CLAUDE.md`/`AGENTS.md`/a Makefile target and re-run `/add-tests`." Do not fall back to a file-existence heuristic and do not attempt to bootstrap coverage tooling yourself — a low-fidelity guess standing in for real coverage data is worse than stopping. `integration` may be `null`; that only affects the tier-routing decision in step 6, it never blocks t