Copilot Skill: project-handoff
# Copilot Skill: project-handoff
## Intent
Create durable handoff documents such as `assessment.md`, `project-analysis.md`, or `handoff.md` after substantial repo work.
Use this skill when a future engineer or AI agent needs enough context to resume without rescanning the whole repository.
## Use When
- The user asks for an assessment, analysis, handoff, or resume context file
- Substantial repo work has been completed
- The repo needs a source of truth summary for future sessions
- The user wants next steps, risks, validation, and file ownership captured
## Do Not Use When
- The user only wants a chat summary
- The task is a small one-line change
- The user wants a commit message or PR description
## Workflow
1. Inspect the repo tree and changed files.
2. Read the README, changelog, tracking docs, workflows, and main source files relevant to the work.
3. Identify what is current source of truth.
4. Summarize completed work, current state, validation, risks, and next steps.
5. Choose the handoff filename based on repo convention:
- `assessment.md` for broad repo assessment
- `project-analysis.md` for project state and recommendations
- `handoff.md` for session continuation
6. Keep the file practical and repo-specific.
## Output Format
Use this structure:when to use it
Community prompt sourced from the open-source GitHub repo mickpletcher/AI-Skills (NOASSERTION). A "Copilot Skill: project-handoff" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
mickpletcher/AI-Skills · NOASSERTION
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions