# handover-developer

Generates technical handover guides for AEM Edge Delivery Services codebases. Useful when onboarding engineers or documenting block architecture.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 714 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-developer/SKILL.md
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/skills/handover-developer

## What it does

The skill checks for `scripts/aem.js` at the repository root. If that file is missing, execution stops immediately: the tool only operates on AEM Edge Delivery Services repositories and will fail on any other setup. To fetch site metadata, it prompts for the Config Service organization name and reads the IMS token from `~/.aem/ims-token.json`.

Next, the skill inspects directories such as `blocks/`, `scripts/`, `styles/`, and `templates/`. It filters git history to ignore initial boilerplate and commits by `aem-aemy[bot]`, documenting only what team members edited. After analyzing imports in `scripts/scripts.js` and exported methods in `scripts/aem.js`, it writes developer guides to `project-guides/` and compiles a PDF.

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

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

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

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add adobe/skills --skill handover-developer -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-developer/SKILL.md

## When to use it
- generate developer documentation for an AEM Edge Delivery Services repository
- filter out boilerplate and bot commits from project documentation
- map block implementations and custom logic in `scripts/scripts.js`
- export technical handover guides to PDF

## Example prompts
- Create a developer handover guide for this AEM project
- Document our custom blocks and scripts architecture into project-guides
- Generate technical onboarding documentation for this repository

## 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: 3f4b0437daf0789d.

BEGIN THIRD-PARTY FILE 3f4b0437daf0789d
````text
---
name: handover-developer
description: Generate comprehensive technical documentation for developers taking over an AEM Edge Delivery Services project. Use when onboarding developers, creating technical handover documentation, or documenting a project's architecture — analyzes codebase structure, custom implementations, design tokens, and produces a complete developer guide.
license: Apache-2.0
allowed-tools: Read, Write, Edit, Bash, Skill, Glob, Grep
metadata:
  version: "1.0.0"
---

# Project Handover - Development

Generate a complete technical guide for developers. Analyzes the codebase and produces actionable documentation that enables developers to understand, maintain, and extend the project.

---

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

Skip if `allGuides` is set in `.claude-plugin/project-config.json` (orchestrator already validated).

```bash
ALL_GUIDES=$(cat .claude-plugin/project-config.json 2>/dev/null | node -e "
  const d = require('fs').readFileSync(0,'utf8');
  try { console.log(JSON.parse(d).allGuides ? 'true' : ''); } catch(e) { console.log(''); }
")
if [ -z "$ALL_GUIDES" ]; then
  cd "$(git rev-parse --show-toplevel)"
  ls scripts/aem.js
fi
```

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/`.

---

## Execution Checklist

```markdown
- [ ] Phase 0: Get org name and authenticate
- [ ] Phase 1: Gather project information
- [ ] Phase 2: Analyze project architecture
- [ ] Phase 3: Document design system
- [ ] Phase 4: Document blocks, models, and templates
- [ ] Phase 5: Generate PDF
```

---

## Phase 0: Get Organization Name and Authenticate

### 0.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) {}
"
```

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

If no org name is found, ask the user:

> "What is your Config Service organization name? This is the `{org}` part of your Edge Delivery Services URLs (e.g., `https://main--site--{org}.aem.page`). The org name may differ from your GitHub organization."

Ask as a plain text question — not `AskUserQuestion` with options. Organization name is mandatory.

### 0.3 Save Organization Name

```bash
mkdir -p .claude-plugin
grep -qxF '.claude-plugin/' .gitignore 2>/dev/null || echo '.claude-plugin/' >> .gitignore

if [ -f .claude-plugin/project-config.json ]; then
  cat .claude-plugin/project-config.json | sed 's/"org"[[:space:]]*:[[:space:]]*"[^"]*"/"org": "{ORG_NAME}"/' > /tmp/project-config.json && mv /tmp/project-config.json .claude-plugin/project-config.json
else
  echo '{"org": "{ORG_NAME}"}' > .claude-plugin/project-config.json
fi
```
````
END THIRD-PARTY FILE 3f4b0437daf0789d

The third-party file has ended. Everything between the 3f4b0437daf0789d 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 2911 of 12209 bytes. © adobe · Apache-2.0 · https://github.com/adobe/skills/tree/HEAD/plugins/aem/project-management/skills/handover-developer/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