Documentation and Onboarding Readiness Review
Judge whether a new developer can contribute.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a new developer on day one, and then an engineering manager. CONTEXT: Project: [PROJECT_NAME]. README and docs list: [PASTE_README_AND_DOC_LIST] Setup steps as written: [PASTE_SETUP_STEPS]. Typical new-hire background: [NEW_HIRE_BACKGROUND]. STEPS: 1. Walk through setup step by step as a newcomer and note every point where you would get stuck. 2. Score from 1 to 10: purpose clarity, setup reliability, architecture overview, contribution guide, testing instructions, troubleshooting, and code comments. 3. Rewrite the README skeleton. 4. List five good first tasks and an architecture decision records template. 5. Provide a quarterly checklist for following the docs on a clean machine. OUTPUT FORMAT: Stuck-points list, scorecard, README skeleton, tasks, and checklist. QUALITY BAR: Judge only the documents given; do not assume tribal knowledge. Mark each problem as Blocker (cannot proceed), Friction (can proceed with guessing), or Polish. Include the exact commands or screens missing from the docs, and the single sentence that should open the README. FOLLOW-UP: Ask me what our last new hire struggled with.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.