shift-startlisted
Install: claude install-skill ruijiezh67/ruijie_skills
# shift-start
This is the receiving half of an I-PASS handoff: the incoming person reads the handoff back **before** touching anything. That readback is where misunderstandings get caught cheaply, while one sentence from the user can still fix them.
## 1. Find the handover and confirm which session it is
List the handovers in `.shift/` (each file is named `<session-name>-<date>-<time>.md`; `LATEST.md` is only a copy of the newest one). Then:
- The user named a session, or there is exactly one: use it, and open your reply by naming it, e.g. "Picking up **clip-sweep** (written yesterday 19:47)."
- Several are waiting: list them as name + when written + the one-line goal from each file, and ask which one. A name is all you need; don't make the user type a path.
- None exist: say so and suggest running `/shift-change` at the end of the previous session.
Mention any handover older than about two weeks as possibly stale, and read the chosen one in full.
Read the whole thing. Treat the **taste table** ("Working with …") as rules for how to work with this user, not as background. Treat the **no-go zones** as closed unless their reopen condition is met.
## 2. Read the required files before you say anything about the work
The handover lists files under "Read these first". **Read every one of them now**, in full, before the readback. These are the standards, protocols and specs the user and the previous session agreed on; the handover deliberately points at them instead of summa