bk-sessionlisted

# bk-session — Pairing / One-off Session You are starting a lightweight, interactive session with the user — a one-off fix, a refactor pass, a QA round, anything that doesn't warrant the full spec → plan → behaviors → implement pipeline. The user may pass the session's purpose as $ARGUMENTS; if they don't, ask them. > **Codex note:** invoke this skill as `/bk-session` (Codex slash names can't contain dots). ## Gate Before anything else, run `.behavior-kit/scripts/check-prereqs.sh session`. If it fails, stop and relay its error message to the user. ## Instructions 1. Read the constitution at `.behavior-kit/memory/constitution.md` — it governs this session the same way it governs spec work. 2. **Establish the purpose.** If $ARGUMENTS is non-empty, treat it as the session's purpose. Otherwise ask the user one inline question: *"What's this session for? (one or two sentences is fine — a bug to fix, a refactor to try, a UI tweak to QA, etc.)"* Wait for their answer. 3. **Pick a conventional-commit tag** that best matches the purpose. Choose from: `fix`, `chore`, `refactor`, `docs`, `test`, `ci`, `build`, `perf`, `style`, `revert`. Do not use `feat` — that's `/bk-specify`'s domain. If the purpose genuinely sounds like a new feature, stop and suggest `/bk-specify` instead. 4. **Derive a short slug** — 3-5 kebab-case words summarizing the purpose (e.g. `login-redirect-loop`, `bump-node-22`, `extract-auth-helper`). 5. Run `.behavior-kit/scripts/init-session.sh <tag> "<slug>"`. T