coding-agent-toolkit

This skill should be used at the START of any non-trivial work unit, when the user asks to "align", "spec this out", "define the work", or before planning/implementing. Forcefully interrogates the user (or seeds the spec from a brief/RFC if invoked as `/align @brief.md`) to produce a complete spec.md (WHAT/WHY end-state) that the headless `plan` step can consume without further questions.

This skill should be used when the user asks to "write a handoff", "produce a transition", "record where we are for the next session", "write a digest before /clear", or runs `/handoff`. Writes a durable transition file at `.workspace/transitions/YYYY-MM-DD/HHMMSS.md` that any future session on either host (Claude or Codex) can pick up cold via `/continue`. Host-neutral.

This skill should be used after all issues in a milestone have commits on the milestone's PR branch and the user asks to "ship the milestone", "merge the PR", "close out the milestone", or runs `/ship`. Verifies every milestone issue has a closing-footer commit on the PR branch, marks the PR ready if draft, squash-merges with branch deletion, verifies all milestone issues auto-closed, closes the milestone, and writes a transition entry. Host-neutral — same contract on Claude and Codex.

This skill should be used when the user says "continue from <transition-file>", asks to "resume from the last handoff", "pick up where we left off", or runs `/continue`. Reads a transition file written by `/handoff`, runs its verification snapshot, reports drift, and surfaces the suggested next steps WITHOUT auto-executing. Host-neutral.

This skill should be used after `/plan-issues` has materialized issues on GitHub and the user asks to "implement the next issue", "pick up the next ticket", "do the next one", or runs `/next-issue`. Picks the lowest-numbered open issue in the active milestone, branches if needed, implements per the issue body, runs tests, commits with `Closes

This skill should be used after a `plan.md` exists in an active work unit, when the user asks to "create the issues", "open the GitHub issues from the plan", "materialize issues", or runs `/plan-issues`. Parses `plan.md`, creates the milestone, and opens one GitHub issue per `**Issue N — <title>**` heading. Default is dry-run; pass `--apply` to actually create.