From game-porting-skills
Closes out the current milestone by prompting a commit, updating porting-memory.md, writing a handoff note, and updating the goal document milestone status.
How this skill is triggered — by the user, by Claude, or both
Slash command
/game-porting-skills:porting-handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are entering Phase 4: Handoff for the current milestone.
You are entering Phase 4: Handoff for the current milestone.
Locate the agent's artifact directory at <project-root>/.porting/ (defined in porting-methodology). All artifacts live there. Load the porting-methodology skill if not already in context.
Ask the user to commit any uncommitted work before proceeding:
"Before writing the handoff, please commit any uncommitted changes."
Wait for the user to confirm the commit is done.
Read porting-memory.md from the artifact directory and update it:
Determine the current goal name from the goal document (goal-<name>.md). Write a handoff note to the artifact directory as porting-handoff-<goal-name>-M<x>.md (e.g., handoff-basic-rendering-M2.md):
# Handoff: [Milestone Name]
## What Was Done
[One-paragraph summary of the milestone — what was implemented, what's now working]
## Ground Truth Comparison
[Full report of ground truth reference checks performed during validation. For each artifact compared:]
- [Which reference artifact was used (translation-layer capture, RenderDoc XML, etc.)]
- [What was compared (pass structure, draw counts, output textures, resource bindings)]
- [What matched and what diverged]
- [Whether divergences are expected (features not yet implemented) or need investigation]
- [If no ground truths were compared, state why (non-rendering milestone, artifacts unavailable)]
## What's Deferred
[Specific TODOs and STUBs created, with grep patterns]
- `grep "STUB(M<next>)"` — [description of what these stubs are]
## Known Issues
[Bugs, artifacts, validation warnings not yet fixed]
## Watch For
[Things that will trip you up next milestone — specific, actionable warnings]
## Key Decisions Made
[Why something was done a certain way, so the next session doesn't undo it]
## Skills Needed Next
[Which skills the agent should load for the next milestone]
Read the goal document (goal-*.md in the artifact directory) and update the current milestone's status to "Complete".
Present a summary of all artifacts created or updated:
## Handoff Summary
### Artifacts Updated
- porting-memory.md — [what changed: watch list items added/removed, feature status updates, knowledge added]
- Handoff note — written to <project-root>/.porting/porting-handoff-<goal-name>-M<x>.md
- Goal document — milestone [name] marked Complete
### Next Milestone
[Name and success criterion of the next milestone, or "All milestones complete — run /porting-plan-goal"]
### Watch List (current state)
[Show the current watch list from porting-memory.md so the user can review]
After the user has reviewed the handoff summary:
"Milestone complete. Please start a new session for the next milestone."
Do NOT continue working on the next milestone in this session. The one-session-per-milestone model keeps each milestone's changes bounded and reviewable.
npx claudepluginhub apple/game-porting-toolkit --plugin game-porting-skillsReads goal documents, handoff notes, and relevant skills, then studies code paths to produce a preparation summary for a porting milestone. Does not write code.
Wraps up a work session by recording changed files, caveats, decisions, and next steps so a fresh session can resume without re-deriving context.
Wraps up a finished memex milestone slice by syncing `docs/CONTINUE_HERE.md` (current state, next slice), ticking off `docs/ROADMAP.md` scoreboard items, confirming observations are logged (deferring to memex-observe), and proposing a git tag/commit subject. Use before committing a slice or when handoff docs have drifted from shipped work.