Project Onboarding Binder
Create a single "get productive fast" pack so new joiners stop wasting their first week
Onboarding and handover failures — outdated notes, scattered docs, unclear processes — repeatedly cause wasted time. This recipe generates a living onboarding binder: context, process overview, who's who, where the truth lives, and first-week starter tasks.
INGREDIENTS
PROMPT
Create a skill called "Project Onboarding Binder". Input: a project's artifacts and links (even incomplete). Output: a single onboarding binder that helps a new joiner become productive fast. Requirements: - Produce a structured binder with: context, scope, current plan, key links, glossary, first-week checklist. - Identify which docs are likely to rot and assign ownership + refresh cadence. - Create 3–10 starter tasks tailored to the new joiner's role. Guardrails: - Do not invent links or architecture. If missing, create "TODO link" placeholders. - Keep it practical: optimize for what someone needs in their first week.
How It Works
Provide whatever project artifacts exist (even incomplete): charter, roadmap, backlog,
tool links, team roster. The recipe assembles a single onboarding document that gives a
new joiner everything they need to get productive in their first week — plus doc
ownership rules to prevent the binder itself from rotting.
What You Get
- 1-page project story: why, what, who, when
- Scope summary: in-scope / out-of-scope
- Key links map: single source of truth for docs, tasks, decisions
- Glossary: domain terms and project-specific language
- First-week checklist: observe → contribute → own progression
- Starter tasks: 3–10 tasks tailored to the new joiner's role
- Doc freshness checklist: who maintains what and when
Setup Steps
- Gather project artifacts: charter/brief, roadmap, current backlog
- List tools and where things live (docs, tasks, decisions)
- Provide team roster with roles
- Specify the new joiner's role (engineer, designer, analyst, PM, exec)
- Review the generated binder and share
Tips
- Missing links become "TODO link" placeholders — never fabricated
- Audience-aware: adjust depth for engineers vs execs
- Doc format: Google Doc, Confluence, or Markdown
- Refresh cadence: monthly, per release, or quarterly (configurable)
- Best created before the new person starts, not on day one