Start of a non-trivial work unit, before planning or implementing: "align", "spec this out", "define the work", or /align (optionally /align @brief.md). Interrogates the user into a complete spec.md.
"continue from ", "resume from the last handoff", "pick up where we left off", or /continue. Resumes from a /handoff transition file and reports drift without auto-executing.
This skill should be used when the user asks to "message another session", "ask the other agent", "delegate to a peer session", "coordinate with the session in my other pane/worktree", "tell the session ...", "check on the migration/test run in the other terminal", "see what the session is doing", "inspect/peek at…
"write a handoff", "produce a transition", "record where we are for the next session", "write a digest before /clear", or /handoff. Writes a transition file any later Claude or Codex session resumes from via /continue.
After /plan-issues: "implement the next issue", "pick up the next ticket", "do the next one", or /next-issue. Implements the lowest-numbered open issue in the active milestone and commits with a closing footer.
After every milestone issue has a commit on the PR branch: "ship the milestone", "merge the PR", "close out the milestone", or /ship. Squash-merges, closes the milestone, writes a transition entry.
After /align wrote spec.md: "plan this", "decompose the spec", "break this into issues", or /decompose. Produces the plan.md that /plan-issues parses. Claude Code's built-in /plan prefix does NOT reach this step.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: