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.
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.
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.
From repo access to first merged PR, fast
Onboard new engineers, QA, DevOps, and PMs without tribal knowledge. Standardize access, environment setup, architecture orientation, and a first safe change.
Navigate a large codebase by tracing real flows, not reading everything
Reduce "where do I start?" paralysis in large systems by generating an executable map: entrypoints, critical paths, ownership, and safe starter changes.
Ship new creatives every week without chaos
Creative teams burn out when "we need new ads" arrives as an emergency. This recipe creates a weekly sprint system: inputs, brief template, production checklist, QA, and a testing plan that compounds learning.
Checklist-first entries to reduce forced trades
Many traders report taking trades that "aren't really their setup" during quiet periods. This forces a short checklist before any order template is generated.