Cc Sdd New Agent
gotalab/cc-sdd
Add or extend coding-agent support in cc-sdd by executing the SOP in docs/cc-sdd/sop-new-agent.md end-to-end.
Writes a handover document so another person, another agent, or a different tool can pick up multi-session work cold.
Install Vibe Handover Doc
$ npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ash1794/vibe-engineering vibe-handover-doc --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-handover-doc .claude/skills/vibe-handover-doc && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibe-handover-doc" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-handover-doc into .claude/skills/vibe-handover-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-handover-doc", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-handover-docType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ash1794/vibe-engineering vibe-handover-doc --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-handover-doc .agents/skills/vibe-handover-doc && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-handover-doc" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-handover-doc into .agents/skills/vibe-handover-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-handover-doc", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ash1794/vibe-engineering vibe-handover-doc --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-handover-doc .cursor/skills/vibe-handover-doc && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibe-handover-doc" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-handover-doc into .cursor/skills/vibe-handover-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-handover-doc", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ash1794/vibe-engineering.git --path plugins/vibe-engineering/skills/vibe-handover-doc--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ash1794/vibe-engineering vibe-handover-doc --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-handover-doc .gemini/skills/vibe-handover-doc && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibe-handover-doc" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-handover-doc into .gemini/skills/vibe-handover-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-handover-doc", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ash1794/vibe-engineering vibe-handover-docInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-handover-doc .github/skills/vibe-handover-doc && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibe-handover-doc" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-handover-doc into .github/skills/vibe-handover-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-handover-doc", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ash1794/vibe-engineering vibe-handover-doc --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-handover-doc .opencode/skills/vibe-handover-doc && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibe-handover-doc" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-handover-doc into .opencode/skills/vibe-handover-doc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-handover-doc", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibe-handover-doc- GitHub stars
- 163
- Token cost
- ~893 tokens
- SKILL.md length
- 496 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes a handover document so another person, another agent, or a different tool can pick up multi-session work cold.
- Works in 6 steps: Capture state from the repo, not from… → Document completed work — What was done,… → Document remaining work — What's left,… → …
- Handing work to someone else
- SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Steps and Wind-Down Mode (usage limit,…, plus 1 more section
- Calls git
What it does
Vibe Handover Doc is an agent skill from ash1794/vibe-engineering. Writes a handover document so another person, another agent, or a different tool can pick up multi-session work cold. Use when handing work to someone else, switching tools, or pausing work that will not resume in the same session.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.
When your agent uses it
- Handing work to someone else
- Switching tools
- Pausing work that will not resume in the same session
Example prompts
- “Use the vibe-handover-doc skill to write a handover document so another person, another agent, or a different tool can pick up multi-session work cold”
- “/vibe-handover-doc”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Capture state from the repo, not from memory
- Document completed work — What was done, key decisions (link vibe-decision-journal entries), problems solved and how.
- Document remaining work — What's left, what's blocked and on what, known issues introduced, and approaches already tried and rejected (so…
- Write a resume prompt — A self-contained prompt the next session can be started with: branch, files to read first, the next concrete task…
- Order it current-state-first. The top of the doc is what the next reader acts on. Move superseded plans and history to the bottom or to a…
- Save to docs/handover/YYYY-MM-DD-.md (or docs/HANDOVER.md for a single rolling doc), and commit it if the next reader will work from a…
What it can do on your machine
Read from SKILL.md and the folder at commit 8f1d71b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibe Handover Doc loads about 893 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 496 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 496 words, ~893 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-handover-doc/SKILL.md (or your agent's skills folder).- name
- vibe-handover-doc
- description
- Writes a handover document so another person, another agent, or a different tool can pick up multi-session work cold. Use when handing work to someone else, switching tools, or pausing work that will not resume in the same session.
- user-invocable
- true
vibe-handover-doc
Within one session, the harness handles continuity: context compaction, session resume, and memory files. A handover doc is for the moment that breaks: a different person, a different agent tool, or a fresh session days later. Write it for a reader who has none of your context.
When to Use This Skill
- Handing work to a teammate or another agent
- Switching tools mid-project (for example, Claude Code to Codex or Gemini CLI)
- Pausing multi-session work that won't resume via session resume
- User says "save progress", "let's continue tomorrow", or "write this up for X"
When NOT to Use This Skill
- To free up context in the current session (the harness compacts automatically; if you want to compact early, use its own command)
- Short sessions with trivial tasks
- Work that is fully committed, tested, and described in the PR (the PR is the handover)
- A current handover doc already exists (update it instead)
Steps
Capture state from the repo, not from memory:
- Branch, last commit,
git status(uncommitted changes?) - Test status: run the suite and record pass/fail, don't guess
- Open PR, CI state, unresolved review threads
- Branch, last commit,
Document completed work — What was done, key decisions (link
vibe-decision-journalentries), problems solved and how.Document remaining work — What's left, what's blocked and on what, known issues introduced, and approaches already tried and rejected (so the next person doesn't retry them).
Write a resume prompt — A self-contained prompt the next session can be started with: branch, files to read first, the next concrete task, and how to verify it.
Order it current-state-first. The top of the doc is what the next reader acts on. Move superseded plans and history to the bottom or to a separate file; a resume file that grows into a history slows every pickup.
Save to
docs/handover/YYYY-MM-DD-<topic>.md(ordocs/HANDOVER.mdfor a single rolling doc), and commit it if the next reader will work from a fresh clone.
Show full SKILL.md (173 more words)Show less
Wind-Down Mode (usage limit, restart, or "stop for now")
When a session must stop mid-work, especially with agents running:
- Stop or message running agents to reach a safe point
- Commit what passes its checks; stash or commit half-done edits to a clearly named WIP branch or stash, and record where
- Record CI state per pushed commit
- Write the handover with exact resume steps (a
CONTINUE.mdat the root works well) - Put the resume convention in the project instructions file, for example "on 'continue', re-read CONTINUE.md and resume from the first unfinished step"
When the owner says pause ("just note it down"), write the note and plan, then stop. Don't keep building.
Output Format
Handover: [Feature/Project Name]
Date: [today] · Branch: [branch] · Last commit: [sha] Tests: [pass/fail counts, command used]
Completed
- [task]
Remaining
- [task] — [notes]
- [task] — blocked by [X]
Decisions & Dead Ends
- [decision] — [rationale / DEC-ID]
- Tried [approach], rejected because [reason]
Known Issues
- [issue] — [impact]
Resume Prompt
[Self-contained prompt: context, branch, files to read first, next step, how to verify.]
© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/vibe-engineering/skills/vibe-handover-doc of ash1794/vibe-engineering.
Open the folder on GitHubat commit 8f1d71b
Compare with similar skills
Vibe Handover Doc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibe Handover Doc this skillash1794/vibe-engineering | 163 | — | ~893 | Automated safety check: Pass | MIT | |
| Cc Sdd New Agentgotalab/cc-sdd | 3.7k | — | ~1.1k | Automated safety check: Pass | MIT | |
| DBS Business Toolkit Entrydontbesilent2025/dbskill | 11k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Tradingagents AnalysisKylinMountain/TradingAgents-AShare | 857 | — | ~1.8k | Automated safety check: Pass | Custom licence | |
| Dr Manhattanguzus/dr-manhattan | 204 | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Polymarket Tennislivetennisapi/livetennisapi-mcp | 152 | — | ~3k | Automated safety check: Pass | MIT |
Similar skills
DBS Business Toolkit Entry
dontbesilent2025/dbskill
Chinese-language entry skill for the dontbesilent business toolkit: onboards new users, orchestrates tasks across sub-skills, runs numbered prompts and lists hidden ones.
Tradingagents Analysis
KylinMountain/TradingAgents-AShare
A股多智能体 AI 投研分析工具 — 15 名 AI 分析师协作完成技术分析、基本面分析、 市场情绪研判、资金流向追踪（北向资金/主力资金）、宏观经济分析及博弈论推演， 输出结构化买卖建议与风险评估。支持沪深 A 股股票代码和中文名称。
Dr Manhattan
guzus/dr-manhattan
Trade prediction markets (Polymarket, Kalshi, Opinion, Limitless, Predict.fun) using a unified CCXT-style API.
Polymarket Tennis
livetennisapi/livetennisapi-mcp
Build observe-only Polymarket and Kalshi tennis market tooling on the polymarket-tennis Python package (MIT) plus the Live Tennis API free tier.
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
More from ash1794/vibe-engineering
All 33 skills in this repoVibe Concurrent Test Safety
ash1794/vibe-engineering
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.
Vibe Fuzz Parser Inputs
ash1794/vibe-engineering
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).
Vibe Golden File Testing
ash1794/vibe-engineering
Implements snapshot/golden file tests with temporal normalization so tests don't break daily.
Vibe Parallel Task Decomposition
ash1794/vibe-engineering
Analyzes large tasks for independent subtasks that can be safely parallelized.
Vibe Slop Filter
ash1794/vibe-engineering
Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).
Vibe Spec Sync
ash1794/vibe-engineering
Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.
Related
Categories
Questions about Vibe Handover Doc
What does Vibe Handover Doc do?
Writes a handover document so another person, another agent, or a different tool can pick up multi-session work cold. Vibe Handover Doc is an agent skill from ash1794/vibe-engineering. Writes a handover document so another person, another agent, or a different tool can pick up multi-session work cold.
When should I use Vibe Handover Doc?
Vibe Handover Doc fits situations like: handing work to someone else; switching tools; pausing work that will not resume in the same session.
How do I install Vibe Handover Doc in Claude Code?
Run `npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-handover-doc in ash1794/vibe-engineering) into .claude/skills/vibe-handover-doc in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Handover Doc in Codex?
Run `npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-handover-doc in ash1794/vibe-engineering) into .agents/skills/vibe-handover-doc in your project. Codex loads it when a task matches its description.
Can I use Vibe Handover Doc in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ash1794/vibe-engineering --skill vibe-handover-doc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-handover-doc, .gemini/skills/vibe-handover-doc, .github/skills/vibe-handover-doc and .opencode/skills/vibe-handover-doc in your project.
What does Vibe Handover Doc need to run?
Going by SKILL.md and its folder, Vibe Handover Doc needs the command-line tools its instructions call (git).
Does Vibe Handover Doc access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Vibe Handover Doc safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vibe Handover Doc use?
Vibe Handover Doc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibe Handover Doc use?
About 893 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vibe Handover Doc?
Skills that share tags, products or a category with Vibe Handover Doc: Cc Sdd New Agent (gotalab/cc-sdd, 3.7k stars), DBS Business Toolkit Entry (dontbesilent2025/dbskill, 11k stars), Tradingagents Analysis (KylinMountain/TradingAgents-AShare, 857 stars) and Dr Manhattan (guzus/dr-manhattan, 204 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Handover Doc?
ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.