claude-code-config: Skill for Claude Code

Generate a PM handoff prompt for starting or continuing a PM orchestration thread. This prompt is self-contained — paste it into a new Claude Code session (web or CLI) and the new thread becomes the project manager for this repo, with full awareness of what the previous PM thread was doing.

Resolve the config parser before Step 1:

resolve_script() {
  local name="$1" candidate
  for candidate in \
    "$HOME/.claude/skills-worktree/.claude/scripts/$name" \
    "$HOME/.claude/scripts/$name" \
    ".claude/scripts/$name"; do
    if [[ -x "$candidate" ]]; then echo "$candidate"; return 0; fi
  done
  return 1
}
PM_CONFIG_GET_SH=$(resolve_script pm-config-get.sh || true)
[[ -n "$PM_CONFIG_GET_SH" ]] || { echo "ERROR: pm-config-get.sh not found (checked all three paths) — PM handoff config capture unavailable" >&2; exit 1; }

Parse $ARGUMENTS:

• If $ARGUMENTS contains "copy" or "clipboard", copy the final output to clipboard via pbcopy in addition to stdout.
• If empty, output to stdout only.

Step 1: Detect mode (bootstrap vs. standard)

Probe for the config file via the shared parser. pm-config-get.sh returns rc=2 for two distinct conditions it does not itself distinguish — "file missing" and "file exists but unreadable" (see its EXIT STATUS contract) — so disambiguate here with a plain existence check before dispatching. Skipping this check means a permissions glitch or transient filesystem issue on an existing config would be silently overwritten by Step 2's bootstrap.

CONFIG_FILE=".claude/pm-config.md"
"$PM_CONFIG_GET_SH" --list >/dev/null 2>&1
CONFIG_RC=$?

if [[ "$CONFIG_RC" -eq 0 || "$CONFIG_RC" -eq 1 ]]; then
  MODE="CONFIG_EXISTS"
elif [[ "$CONFIG_RC" -eq 2 && ! -e "$CONFIG_FILE" ]]; then
  MODE="BOOTSTRAP"
else
  MODE="UNREADABLE"
fi

CONFIG_RC 0 or 1 both mean the file was read successfully (1 just means zero sections or an empty section body — see the script's EXIT STATUS contract), so both map to CONFIG_EXISTS. Anything else — rc=2 with the file present, a usage error (rc=3), or any other unexpected exit code — maps to UNREADABLE rather than being silently treated as a healthy config.

• If MODE == BOOTSTRAP (file genuinely absent): proceed to Step 2 (create config from repo scan)
• If MODE == UNREADABLE (file exists but pm-config-get.sh returned an error for it, or returned an exit code outside the documented contract): STOP. Tell the user: ".claude/pm-config.md exists but could not be read — check file permissions and encoding before continuing." Do NOT proceed to Step 2 — bootstrapping here would silently overwrite the existing file's content, including any user-customized Role/OKRs/Team/Notes sections and any non-canonical sections.
• Otherwise (CONFIG_EXISTS): skip to Step 3 (read existing config)