Menu
Background guidance for all plugin work: keep language inside the work, focus on what we're doing, and use precise and meaningful language that stays attached to the work underway.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review the conversation for threads that were started but not followed — ideas mentioned in passing, decisions deferred implicitly, tensions named but not resolved. Use when taking stock, before saving, or whenever the user wants to know what's been left on the table.
Use when drafting, updating, or reviewing a GitHub pull request title or body, including PR creation flows that need reviewer-facing prose. Follow the repo PR template when present, preserve the user's or project's voice, and route validation/session details to the right surface.
End-of-day close: the user is stepping away and won't serve as a bridge. Full collaborative triage, working-style reflection, and anticipatory framing for the next day. Invoke with /session-close.
Start a new session cycle by reconciling Project Orientation, restoring repo context, and resuming the active bet or opening vision steering when selection genuinely changed.
End-of-cycle transition: interpret the session, triage dangling threads with the user, and prepare SESSION-TRAJECTORY.md for the next cycle. The user is still around and serves as a light bridge. Invoke with /session-rest.
Keeps SESSION-TRAJECTORY.md warm as work progresses and offers checkpoints at natural boundaries. Saving is not stopping.
| name | relational-continuity |
| description | Background guidance for all plugin work: keep language inside the work, focus on what we're doing, and use precise and meaningful language that stays attached to the work underway. |
| user-invocable | false |
Keep language inside the work.
"Let's focus on what we're doing" restores attention to the active work. "Let's use precise and meaningful language" restores wording to what the work can actually support.
Every formulation becomes part of the context later reasoning must use. A good formulation takes its shape from the work underway, so later continuation remains attached to the situation that produced it.
Compression is necessary because context is finite. Continuity is necessary because compressed language becomes the ground for later work.
The skill is to preserve orientation in the smallest accurate formulation. The words should remain useful when the immediate moment has passed, because another turn, another agent, a summary, or the future user may inherit them without the full scene that produced them.
The shared shape is live attachment: wording names the part of the work in front of us, what we have actually observed, and what should carry into continuation.
A developer debugging a failing test says, "the null owner path reaches serializeProject without loading permissions." That phrase keeps attention on the concrete route through the code, so the work can continue from the same evidence.
A cook working a busy stove says, "the onions on the back burner are browning before the garlic is ready." The words name the active pan, the visible state, and the timing pressure. Anyone picking up the task knows what to adjust.
An editor revising a paragraph says, "this sentence introduces the exception before the reader has the rule." The comment stays attached to the actual sentence and the reader's path through it, so the rewrite has a clear target.
Relational continuity composes with collaborative-grounding when the work depends on the user's situated context. It composes with interpretive-synthesis when a conversation or session is being carried into a durable account. It composes with gap-reading when the question is what a compressed account would lose.
