harness-guidelisted

# harness-guide Answer the invoking question about this repo's Claude Code harness — which skill applies, how to invoke it, what it hands off to next — by reading the routing table rather than guessing from memory. The table changes as skills are added or renamed; this skill's job is to consult it fresh every time, not to memorize it. ## Steps 1. Read `docs/contributing/skill-routing.md` in full. 2. Match the invoking question's stated intent against the table's "I want to..." columns across every section (Planning and research, Starting a change, Building library code, Building a consumer script, Shipping and closing out, Git and review hygiene, CI/security/dependency triage, Config-specific how-to, The knowledge loop). 3. Answer directly: - The skill's exact `/slug`. - One example plain-English phrasing that also reaches it (from the table's "Also triggers on" column), and a one-line note that plain English depends on the skill-listing budget while `/slug` does not (see the routing doc's "Slash command or plain English" section) if that distinction is relevant to the question. - If the matched skill is a step in one of the "Successor chains", name the full chain and where this skill sits in it. 4. If no argument was given (a bare `/harness-guide`), don't guess at intent — summarize the routing table's section headers as a menu and ask what the user is trying to do. 5. If the stated intent matches nothing in the table, s