# handover

Generates handover documentation for an AEM Edge Delivery Services project: separate guides for content authors, developers and site administrators.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1500 installs · ★ 310
- Author: adobe
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/adobe/skills/tree/HEAD/plugins/aem/project-management/skills/handover/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/handover

## What it does

The skill starts at the git repo root. It runs `cd "$(git rev-parse --show-toplevel)"` and looks for `scripts/aem.js`. If that file is missing, it stops and says a project with Edge Delivery Services is required. Plain repositories are out.

\`AskUserQuestion` offers four choices: all three guides, authoring only, developer only, admin only. Next comes the Config Service organization name. Type it, or paste a `*.aem.page` URL and the skill extracts the org from the host. The value goes to `.claude-plugin/project-config.json` along with an allGuides flag when you picked every guide, and that folder is appended to `.gitignore`.

Before writing anything, the skill reads `~/.aem/ims-token.json`. An expired or absent token triggers the `aem-project-management:auth` skill; afterwards the org name is verified against `admin.hlx.page`. Choosing all three launches three subagents in one message, running side by side. Output lands in `project-guides/`. A wrong org name gets flagged by the check, and the skill asks again.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill handover -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/handover/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/handover/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill handover -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/handover/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill handover -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/handover/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install adobe/skills handover
```

2. **Manually: put the files in place**
- File: `.github/skills/handover/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill handover -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/adobe/skills --path plugins/aem/project-management/skills/handover
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/handover/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill handover -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/adobe/skills/tree/HEAD/plugins/aem/project-management/skills/handover/SKILL.md

## When to use it
- produce an authoring guide covering blocks and templates
- document the codebase and design tokens for new developers
- write an admin guide on permissions, API operations and cache
- ship all three guides at once during a project handoff
- verify the org name before docs are generated

## Example prompts
- Generate the handover docs for this project, all three guides
- Make just the Developer Guide from this repo
- Build the authoring guide, take the org from our preview URL

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 5b3d1f7946301251.

BEGIN THIRD-PARTY FILE 5b3d1f7946301251
````text
---
name: handover
description: Generate project handover documentation for AEM Edge Delivery Services projects. Creates comprehensive guides for content authors, developers, and administrators. Use for "handover docs", "project documentation", "generate handover", "create guides".
license: Apache-2.0
allowed-tools: Read, Write, Edit, Bash, AskUserQuestion, Skill, Agent
metadata:
  version: "1.1.0"
---

# Project Handover Documentation

Generate comprehensive handover documentation for Edge Delivery Services projects. Orchestrates the creation of guides for different audiences.

## Available Documentation Types

| Guide | Audience | Skill |
|-------|----------|-------|
| **Authoring Guide** | Content authors and content managers | `handover-author` |
| **Developer Guide** | Developers and technical team | `handover-developer` |
| **Admin Guide** | Site administrators and operations | `handover-admin` |

---

## Execution Flow

### Step 0: Navigate to Project Root (MANDATORY)

```bash
cd "$(git rev-parse --show-toplevel)"
ls scripts/aem.js
```

If `scripts/aem.js` does not exist, tell the user this skill requires an AEM Edge Delivery Services project and stop.

All subsequent steps operate from project root. Guides are created at `project-guides/`.

---

### Step 0.5: Clean Up Stale Config

```bash
rm -f .claude-plugin/project-config.json
```

---

### Step 1: Ask User for Documentation Type

Use `AskUserQuestion` with exactly these 4 options:

```json
AskUserQuestion({
  "questions": [{
    "question": "Which type of handover documentation would you like me to generate?",
    "header": "Guide Type",
    "options": [
      {"label": "All (Recommended)", "description": "Generate all three guides: Authoring, Developer, and Admin"},
      {"label": "Authoring Guide", "description": "For content authors and managers - blocks, templates, publishing"},
      {"label": "Developer Guide", "description": "For developers - codebase, implementations, design tokens"},
      {"label": "Admin Guide", "description": "For site administrators - permissions, API operations, cache"}
    ],
    "multiSelect": false
  }]
})
```

### Step 1.5: Get Organization Name

After the user selects guide type(s), ensure the organization name is available before invoking any sub-skills.

#### 1.5.1 Check for Saved Organization

```bash
cat .claude-plugin/project-config.json 2>/dev/null | node -e "
  const d = require('fs').readFileSync(0,'utf8');
  try { const o = JSON.parse(d).org; if(o) console.log('org: ' + o); } catch(e) {}
"
```

#### 1.5.2 Resolve Site Name from Git

```bash
SITE=$(basename -s .git $(git remote get-url origin 2>/dev/null) 2>/dev/null)
echo "site=${SITE:-NOT SET}"
```

#### 1.5.3 Prompt for Organization Name (If Not Saved)

If no org name is saved, ask the user:
````
END THIRD-PARTY FILE 5b3d1f7946301251

The third-party file has ended. Everything between the 5b3d1f7946301251 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2801 of 10088 bytes. © adobe · Apache-2.0 · https://github.com/adobe/skills/tree/HEAD/plugins/aem/project-management/skills/handover/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md