Choose one of three approaches. The steps for that option appear below.
Choose an option above. On a phone, swipe the tabs left or right to see all options →
Cursor drafts steps, guide and test sheet; you check versions and sources before a newcomer tests on a clean machine.
Collect the repository and onboarding
Draft steps, guide
Test the approved guide and
Use: You
Have ready: current repository, README fragments, Makefile, scripts and complete onboarding thread notes in the Cursor workspace.
Proprietary code goes into an external tool only if your organisation's rules allow it.
Use: Cursor
Ask Cursor for steps and versions, then guide and test sheet; check pinned versions and approve ordering before each dependent draft.
What to paste into the tool
Task: Draft step list (Numbered list with versions). Read the Makefile, README fragments and these onboarding notes. Draft a numbered setup step list for a new developer, naming each tool and the version exactly as pinned or stated. Mark any step where the sources disagree. Task: Draft guide (Markdown guide with numbered steps). Write a Markdown setup guide from this checked step list: numbered steps, versions as given, and a troubleshooting section drawn only from the repo files and onboarding notes. Task: Draft newcomer test sheet. Turn each numbered step of this guide into a test sheet row: step number, what to do, expected result, and a blank field for what actually happened.
Use: The new developer
Follow the approved guide exactly on a clean machine; record every failure's step number for the team lead to collect and fix.
Versions must come from the repo or notes. Remove unsupported steps and troubleshooting. Check the test sheet covers every guide step in order.
Replit (Replit Agent) drafts steps and guide; you approve sources and write the test sheet before a newcomer tests.
Import the repository and onboarding
Draft ordered steps
Check the guide and write
Test the guide on a
Use: You
Have ready: repository, scripts and onboarding chat; import the current repository and complete notes into Replit (Replit Agent).
Proprietary code goes into an external tool only if your organisation's rules allow it.
Use: Replit (Replit Agent)
Ask Replit (Replit Agent) for tools, pinned versions and ordered steps; check versions before requesting a guide using only repository troubleshooting.
What to paste into the tool
Task: Draft step list (Numbered list with versions). Read this repo and these notes. Draft a numbered setup step list for a new developer, naming each tool and the version exactly as pinned or stated. Mark any step where sources disagree.
Use: You
Check the guide against the checked steps, repository and notes; approve ordering and troubleshooting, then write one test-sheet row per guide step.
Hold the drafted guide as unchecked until the lead approves it. Remove unsupported steps; check the sheet covers every guide step in order. Versions appear only as supplied.
Use: The new developer
Follow the approved guide exactly on a clean machine; record every failure's step number for the team lead to collect and fix.
Coda drafts from supplied repository material; you check versions and approve the guide before a newcomer tests it.
Collect repository material
Draft ordered steps, guide
Check ordering, troubleshooting and sheet
Test on a clean machine
Use: You
Have ready: README, Makefile, scripts and onboarding thread; paste the complete source material into a Coda document.
Proprietary material goes into an external tool only if your organisation's rules allow it; this record does not establish that upload is permitted.
Use: Coda
Ask Coda for pinned-version steps, then guide and test sheet; check each step and version before the next draft.
What to paste into the tool
Task: Step list (Numbered list with versions). Draft the setup step list from only the material in this doc: numbered steps, tools and versions exactly as pinned or stated there. Add no tools, steps or versions of your own; where the material does not give a version, leave a marked gap. Task: Draft guide (Markdown guide with numbered steps). Draft a setup guide from only the checked step list and notes in this doc: numbered steps, versions exactly as given, and a troubleshooting section from the notes. Add no tools or versions of your own. Task: Newcomer test sheet table. Generate a table with one row per guide step: step number, what to do, expected result, and an empty column for what actually happened.
Use: You
Compare the guide with checked steps and notes; remove unsupported material, approve ordering and troubleshooting, and check one test row per step.
Versions appear only as supplied.
Use: The new developer
Follow the approved guide exactly on a clean machine; record every failure's step number for the team lead to collect and fix.
Best when: You want repository reading and all three drafts in one workspace.
What it does: Cursor drafts steps, guide, test sheet; you check and test
Strong at: Reads repository material to draft ordered steps, guide and test sheet.
Limit: Pinned versions and troubleshooting require checks before the newcomer test.
Free plan: Yes, limited agent features
Best when: You want drafts from an imported repository and human-written test sheet.
What it does: Replit (Replit Agent) drafts steps and guide; you write sheet and test
Strong at: Reads imported repository material and drafts ordered steps and guide.
Limit: You write the test sheet; Free Mode limits apply.
Free plan: Yes, 30 chat hours and 60 projects
Best when: You want document-based drafts from pasted repository material.
What it does: Coda drafts steps, guide, test sheet; you check and test
Strong at: Drafts ordered steps, a guide and a matching newcomer test table.
Limit: You must check pinned versions and source support before testing.
Free plan: Yes, limited attachments
Before you paste into any AI tool, remove any confidential information. Put it back at the end.
Deciding between Cursor and Replit (Replit Agent) for this? See the comparison.
Versions appear only as supplied by the repo or notes.
The team lead approves the guide's ordering and troubleshooting section.
The test sheet covers every guide step in order.
A newcomer follows the guide on a clean machine and lists the step where each problem occurred.
Check data-handling rules before placing proprietary repo material into any tool.
Check the result against your original inputs. Approve it before sharing or acting.