feat(wrap-up): plan-aware branching — emit resume blocks when plan is incomplete

[JacobPEvans]

Summary

• /wrap-up now runs a new Step 0 before the existing cleanup pipeline to decide whether this session's plan is actually done.
• Path A (plan complete or absent) is byte-identical to the prior behavior: /refresh-repo, /retrospecting quick, /clean_gone, then a forward-looking follow-up prompt.
• Path B (plan incomplete) skips Path A — refresh-repo would prune the in-flight worktree — and emits one or more copy-paste Resume Blocks: cd <worktree> plus a self-contained prompt that points at the plan file, lists remaining checklist line numbers + TaskList task IDs, and notes what was already done so a fresh session does not redo work.
• Resume Blocks group by judgement, not by repo alone: same repo + same goal stays together; same repo + unrelated threads split; cross-repo always splits.
• /wrap-up purge-pr <PR> is unchanged and still bypasses Step 0.

Why this matters

The prior /wrap-up assumed the session ended cleanly post-merge. Invoking it mid-plan (context exhaustion, blocker, machine switch) buried unfinished work in the forward-looking follow-up prompt alongside speculative future ideas, which made resuming the exact plan hard. Path B is built for that case.

Identifying the current session's plan

Plan identification uses the plan-mode <system-reminder> already in this session's conversation as the single source of truth — never ~/.claude/plans/ mtime. mtime races under heavy parallelism (many concurrent sessions on the same machine). TaskList is intrinsically session-scoped by the harness, so it is read directly without disambiguation. The path-matching regex is generic ([^[:space:]]+/\.claude/plans/[^[:space:]]+\.md) so the skill works for every plugin user, not one specific home.

URL rule for emitted PR/issue references

Every PR or issue referenced in wrap-up output must use the full https://github.com/<owner>/<repo>/(issues|pull)/<n> URL on first mention — never bare #123, which forces the reader to guess the repo. Codified in the A4c triage step (captures gh issue list --json url), the A4d output template, and the Path B Resume Block "must include" list.

CI / local-validation change

Added cclint (github.com/dotcommander/cclint) as a local precommit hook in .pre-commit-config.yaml — this repo only. Mirrors the loop in .github/workflows/validate-plugin.yml so frontmatter validator failures (e.g. angle brackets in description) fail at commit time instead of escaping to CI. Uses pre-commit's language: golang so contributors do not need a host Go toolchain — pre-commit installs cclint into an isolated env. Loop logic lives in scripts/cclint-plugins.sh per the no-inline-scripts rule.

Verified locally: re-injecting <repo> into the SKILL.md description reproduces the exact CI error message and blocks commit.

Commits

SHA	Subject
be4ed5a	feat: Step 0 + Path A/B routing + Resume Block format
f204dff	fix: strip <repo> angle brackets from description; URL rule; add cclint precommit hook
11700e4	fix: generalize plan-path prose and regex — no user-specific homes (addresses gemini-code-assist review)

Test plan

All verification is human-driven against real Claude Code sessions — no automated tests exist for this skill (it composes other skills + reasoning). CI covers markdown lint, cclint frontmatter validation, and CodeQL.

• Path A regression — fresh session, no plan mode, trivial task, invoke /wrap-up. Expect identical behavior to today.
• Path B basic — session enters plan mode, writes plan with one unchecked item, exits plan mode, does not implement, invokes /wrap-up. Expect one Resume Block citing the exact plan path + Path A skipped + incomplete summary.
• Path B multi-block grouping — plan touching two repos. Expect two blocks with distinct cd paths and self-contained prompts.
• Parallelism regression — two sessions back-to-back, both in plan mode against different plan files; invoke /wrap-up in session A with A's work incomplete. Expect A's plan path cited, never B's, even though B's file is more recently modified on disk.
• purge-pr unchanged — /wrap-up purge-pr <PR> against a throwaway branch. Expect Step 0 bypassed entirely.
• cclint regression — temporarily inject <foo> into any SKILL.md description, run pre-commit run cclint-plugins --all-files, confirm it fails with the Anthropic validator's error message.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request updates the wrap-up skill definition to support a dual-path workflow depending on whether the current session's plan is complete (Path A for clean wrap-up, Path B for emitting resume blocks). The review feedback correctly points out that the plan file paths and regex patterns are hardcoded to a specific user's home directory (/Users/jevans) and provides suggestions to make them generic and environment-agnostic.