What problem does it solve? Developers working with the LiveSpec framework need to remember which CLI subcommand, flags, and exit codes apply to tasks like running tests, checking coverage, or validating the preflight manifest. This Skill acts as an interactive picker that routes requests to the correct livespec subcommand without memorizing the CLI surface. ## Core Features & Use Cases - Subcommand routing: Forwards arguments verbatim to livespec test, coverage, drivers, mutation, or preflight, or asks one clarifying question when invoked with no arguments. - Auto-detection: Resolves project root via .specs/, picks the primary driver, detects the base branch, and reads the coverage threshold from .conventions/index.md without manual flags. - Structured output and exit-code guidance: Surfaces the LIVESPEC <subcommand> summary line and maps non-zero exit codes (1-5) to concrete next steps from docs/cli-reference.md. - Use Case: A developer wants to check patch coverage against the develop branch; invoking the picker with coverage --base develop runs livespec coverage --base develop and reports the summary line and exit code. ## Quick Start Ask the assistant to run the livespec CLI, for example by saying "run livespec coverage against the develop branch and show me the summary line and exit code".
