← ClaudeAtlas

shift-brieflisted

Packages a local sub-task for a collaborator (usually someone who also works with an AI coding agent) as a self-contained bundle. Traces every file the task needs, sanitizes secrets and absolute paths, writes BRIEF.md and START_HERE.md with acceptance criteria as runnable commands plus a paste-ready prompt for the receiver's agent, then has a fresh agent cold-start from the bundle alone and fixes whatever it got stuck on before anything is sent. Use when the user wants to delegate, hand off or assign part of their work to another person, labmate, student or coauthor, e.g. "hand this to my labmate", "package this task for X", "write a task brief", "delegate this". Not for continuing the user's own work in a new session (use shift-change).
ruijiezh67/ruijie_skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill ruijiezh67/ruijie_skills
# shift-brief Handing work to another person fails in predictable ways: a file is missing, a path only exists on your laptop, "done" was never defined, and the receiver's agent has none of the context your session built up. This skill produces a bundle that the receiver's agent can pick up in five minutes, and proves it by having a fresh agent try exactly that before anything is sent. ## 1. Pin down the task State the sub-task back to the user in a few lines: the goal, what is in and out of scope, the deliverable, any deadline, and who receives it. Ask up to 3 questions only where the answer changes the bundle (e.g. "Does the receiver have access to the cluster?", "Chinese, English, or both?"). Everything else you can infer from the session and the repo. ## 2. Trace what the task needs Follow the task from its entry point outward: the scripts it runs, what they import, the configs and data they load, the files this session read or edited for this part of the work, and the outputs it compares against. Details and heuristics are in `references/bundle.md`. Classify every item: - **include**: small source files, configs, notes the receiver needs. - **link**: already reachable (a public repo, a shared drive path, a DOI or URL). - **regenerate**: derivable outputs; give the exact command instead of the file. - **manifest only**: large data; list path, size, sha256 and where to get it. Missing files are the most common failure, so when unsure whether something is needed, list