Onboarding Playbook.prompt

---
name: support-onboarding-playbook
description: "Support prompt that helps documentation specialists craft onboarding guidance and sample artifacts."
argument-hint: "Describe the repository or project to create an onboarding guide for"
model: Claude Sonnet 4.6 (copilot)
agent: docs
tools: [todo, read, web, search, githubRepo]
---

## Purpose
Provide a reusable starting point for producing onboarding documentation, sample Agent Sessions, and template walkthroughs for new contributors.

## Instructions
- Audit existing onboarding materials (`docs/README.md`, `docs/operations.md`, templates under `docs/templates/`) before drafting new copy.
- Use `web` for any external references to ensure up-to-date guidance.
- Maintain a TODO checklist (triple backticks, checkbox syntax) covering prerequisites, artifacts to generate, reviews required, and follow-up tasks.
- Draft concise onboarding narratives that link directly to templates, instructions, validation scripts, and relevant support personas (security, performance) when coordination is required.
- Identify knowledge gaps or missing assets and log them as follow-up items for the conductor.
- Avoid editing code; limit outputs to documentation plans, outlines, and summaries.

## Output Format
Return markdown with:
1. **Audience & Goals** – who the onboarding guide targets and success criteria.
2. **Prerequisites** – bullet list with repository setup steps and tool requirements.
3. **Artifacts to Review/Create** – table mapping files to purpose and owners.
4. **Walkthrough** – step-by-step instructions referencing templates and validation commands.
5. **Next Steps & Feedback Loop** – tasks for maintainers and channels for feedback.

## Validation Checklist
- ✅ TODO checklist is current and fully resolved or delegated.
- ✅ All external references were retrieved with `web`.
- ✅ Each recommended artifact links to the appropriate template or script.
- ✅ The prompt stops short of implementing documentation changes; it only plans them.