Menu
Produce a transition brief and launch command for the user's next interactive primary.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Load when building a static HTML artifact: single page or multi-page site to make structured information explorable through layout and navigation.
Use when deciding where knowledge goes or reading/writing durable docs: AGENTS.md, .context/, KB, docs/, and work directories.
Use when writing or maintaining AGENTS.md, .context/CONTEXT.md, or CLAUDE.md mirrors: keep intent docs minimal and load-bearing.
Anchor work in a work item: artifacts on disk, not in context.
Use when grilling should be grounded primarily in project artifacts. Loads `/grill`, checks project vocabulary and prior decisions first, and spawns bounded explorers when the answer should come from docs.
Load for large human-facing outputs: reports, docs, multi-section explanations, artifacts. Choose the right form for each beat (prose, diagram, table, mockup) and put the answer first, depth behind it. If the medium allows, use progressive disclosure.
| name | handoff |
| type | mode-shift |
| description | Produce a transition brief and launch command for the user's next interactive primary. |
| argument-hint | What will the next session focus on? |
| user-invocable | true |
| model-invocable | true |
Write a transition brief and print a primary launch command. The user runs the command to start a new interactive session with a different agent lead.
If arguments were passed, treat them as the focus for the next session.
Start with /intent-modeling: separate what the human has said from what
they actually want to be true when this work is done. The modeled intent
shapes everything in the brief.
Then compact the conversation into a file the next agent reads as its opening prompt:
Reference artifacts by path; don't duplicate their content.
Write to the active work directory (meridian work current). No work item
→ write to a temp file.
Before completing the handoff, check if any pre-* checkpoint skills are
installed for the next phase (e.g., pre-dev for implementation handoffs).
If present, load and run them to verify workspace, branches, and
prerequisites are ready for the next agent. Skip if none are installed.
Explicit argument wins: /handoff tech-lead.
Otherwise infer from context. If ambiguous, run meridian mars list --json
and ask.
Before printing the launch command, show the user the handoff trail for the active work item so they can see where they've been:
meridian work sessions --primary
Resolve $MERIDIAN_CHAT_ID to the concrete chat ID (e.g., c102): the
user runs this in a new terminal where the env var no longer exists.
meridian -a [agent] \
--work [work-id] \
--task-dir [path] \
--prompt-file [path-to-brief] \
--from [resolved-chat-id]
Use meridian, not meridian spawn (primary launch, interactive). Include
--work when active, --task-dir when in a worktree or sibling repo.