Skip to content

Rehearse onboarding as Anish

Use a disposable copy of the current local branch, so the trial includes changes that are not on GitHub yet. Keep all trial tickets, summaries and XP in that copy. Do not change the identity or records in your working repository.

1. Make an isolated workspace

Run from the real nepwalk-docs root after the latest changes are committed:

trial_root="$(mktemp -d /tmp/nepwalk-rehearsal.XXXXXX)"
git clone --no-hardlinks . "$trial_root/nepwalk-docs"
cd "$trial_root/nepwalk-docs"
git remote remove origin
git switch -c team/anish
pwd

Keep the printed path. The clone has no GitHub remote. Git does not copy the ignored .team-local/profile.json, browser identity or local credentials. Do not add a GitHub remote, push or open real pull requests during this trial.

2. Try the AI onboarding

Open your preferred AI tool in the trial clone. Paste:

This is an isolated onboarding rehearsal. I am Anish, an engineer. Read AGENTS.md and follow the team-onboard skill. Keep all changes in this clone. The team/anish branch already exists. Skip remote fetch, pull, push and PR steps; there is deliberately no origin. Use doctor --offline. Set NEPWALK_TEAM_NO_BROWSER=1 for this rehearsal terminal; I will open the trial dashboard myself in a separate browser profile. Do not change another workspace or claim that missing product setup has passed. Onboard me, then tell me what to do today, one step at a time.

Expected:

  • The AI asks or confirms your identity and claims anish once.
  • The doctor reports that remote access was not checked. Missing FE/BE siblings are expected in a docs-only rehearsal; this is not full engineer readiness.
  • With no assigned tasks, it offers learning without inventing work or XP.
  • Ask which skill it followed. If discovery fails, it should read the skill file directly and continue in plain language.

For a full product trial, clone FE and BE beside the trial docs folder and follow day-one readiness. Use test accounts and a separate development database. Real app checks remain unverified until those apps run.

3. Check the dashboard without switching your real identity

node tools/team.mjs snapshot

Use a new, separate browser profile. Open the trial clone's docs/team/dashboard.html in it and select Anish. This prevents reuse of your normal browser's identity or remembered connection to the real repository. In Chrome or Edge, connect only the trial nepwalk-docs folder.

Check both desktop and phone-sized layouts:

  1. Your progress comes first, then today's tasks and a clear next action.
  2. Anish remains selected after refresh. There is no member-switch control.
  3. Other members' work is readable but has no work, test or acceptance controls for Anish. Assigned reviewers still get their review controls.
  4. Without a connected folder, a copied command checks the same identity before saving. It must stop if the terminal clone belongs to another person.

Run node tools/team.mjs onboard --member prakash in the Anish trial clone once to check the guard. It must refuse, leaving Anish unchanged. Do not reset the file.

4. Rehearse a real assigned task

For task-stage testing, use a second disposable clone for the founder; do not switch the Anish clone's identity. From the Anish trial clone:

git clone --no-hardlinks . ../founder-docs
git -C ../founder-docs remote remove origin
cd ../founder-docs
node tools/team.mjs onboard --member prakash
node tools/team.mjs record task.create '{"id":"rehearsal-dashboard","title":"Check the trial dashboard","brief":"Verify the dashboard in this isolated rehearsal.","acceptance":["Progress appears before tasks on desktop and phone widths","Anish remains selected after refresh"],"assignee":"anish","reviewer":"prakash","priority":"P2","points":5,"kind":"test"}'
git add docs/team/records
git -c core.hooksPath=/dev/null commit -m "test(team): assign isolated rehearsal"
cd ../nepwalk-docs
git fetch ../founder-docs
git merge --ff-only FETCH_HEAD

Tell the AI to start rehearsal-dashboard. Follow its prompts, perform the actual manual checks and describe what you saw. It must wait for human test evidence, then the separate reviewer. It must not accept work as Anish or award task XP yet.

To rehearse acceptance, commit Anish's records locally, fetch and merge that branch into the founder clone, and use the founder's AI to inspect the evidence and review. Niwesh may accept others' P2/P3 tasks; the founder may also accept them. Nobody accepts their own work. Fetch and merge the local founder records back into the Anish clone; accepted task XP should appear once. Regenerate the snapshot and refresh the dashboard after merges.

Only trial commits bypass hooks above because a Git clone does not copy the Python verification environment. Normal team commits must run the repository checks.

5. Try learning, tickets and closure

  • Ask to learn the first AI foundations topic. Explain it in your own words. The AI should ask questions, correct gaps and save a brief summary. Practical application is optional; reading alone must not count as understanding.
  • Report a test bug with a cropped, non-sensitive screenshot. Open the ticket and verify the attachment and reproduction steps. It should remain unassigned.
  • Say "done for today". Give your actual trial hours, including zero if appropriate. Check the summary, unfinished work and next step. No push or PR in this trial.
  • Start a fresh AI session in the same clone and ask for today. Identity, learning and recorded progress should survive; the AI should not ask you to switch people.

Record issues with the action, expected result, actual result and a screenshot. Keep trial results out of the real records. Passing this rehearsal does not prove GitHub sharing, actual engineer accounts, remote CI or FE/BE setup works.