Skip to content

Getting started

Welcome, warrior. Open nepwalk-docs in a terminal, VS Code or Antigravity and use your preferred AI coding tool. Terminal practice is encouraged; the integrated terminal in your editor works too. Say what you need in plain language. The AI reads the team's skills and records the work; the dashboard shows your progress first, then today's tasks.

Trying the setup before rollout? Follow the isolated Anish rehearsal.

The team

Person Member id Role Needs
Prakash prakash Founder: plans, assigns, approves designs, accepts work, merges All three repositories
Niwesh niwesh Manager: assigned testing, UX checks, bug reproduction, fix verification, reviews, accepts P2/P3 work All three repositories, frontend and backend running locally
Shankalpa shankalpa Engineer: builds assigned tasks All three repositories
Anish anish Engineer: builds assigned tasks All three repositories
Umang umang Engineer: builds assigned tasks All three repositories

What you need

  • Git and Node.js 18 or newer.
  • Your own GitHub account with access to the tech-everest repositories. Ask Prakash for access. Never share accounts, passwords or tokens.
  • The GitHub CLI (gh), signed in with your own account, so your AI tool can open pull requests for you. Install it from cli.github.com, then run gh auth login yourself (GitHub.com, HTTPS, log in with a web browser) and check with gh auth status. Never paste the token into a chat.
  • Your own AI coding tool, signed in with your own account. We recommend opencode, run in the terminal (VS Code's or Antigravity's built-in terminal is fine). Any tool that reads AGENTS.md works. Use a strong free model in opencode. Free models may keep what you send, so never paste passwords, .env values, tokens or real customer data into the chat.
  • Read learning pages in your editor or on the docs site. A browser Markdown viewer is optional; for example Markdown Viewer for Chrome, Edge or Firefox. After installing it, open the extension's details and allow access to file URLs, then open any .md file from nepwalk-docs in the browser.
  • Engineers and the manager: whatever nepwalk-fe and nepwalk-be list in their README files.

Set up once

First sign in the GitHub CLI (once per computer): gh auth login, then gh auth status should show your own account.

Put the repositories side by side in one folder:

mkdir nepwalk && cd nepwalk
git clone https://github.com/tech-everest/nepwalk-docs.git
# Engineers and the manager also clone the code repositories:
git clone https://github.com/tech-everest/nepwalk-fe.git
git clone https://github.com/tech-everest/nepwalk-be.git

Then open your AI tool in nepwalk-docs and say "onboard me". It will:

  1. Ask who you are and run node tools/team.mjs onboard --member <your id>. This claims your local workspace once. The name is fixed afterward; it is not a login.
  2. Run node tools/team.mjs doctor and explain each line. MISSING must be fixed, CHECK could not be verified, OPTIONAL is not needed for your role, TODO is your AI sign-in, which the script cannot see.
  3. Create your docs branch: git switch -c team/<your id> origin/main. Your records are saved on it and reach the team through your pull request.
  4. When setup is complete, open your dashboard once. The first "today" request on later days opens it again; repeated requests that day do not open more tabs.
  5. Manager and engineers: start the AI foundations path. Founder: use team oversight; personal development is outside the shared workspace.

Use the doctor report to resolve missing prerequisites. Its ready result does not prove your AI account is signed in or that your editor loaded the skills. Ask the AI to name the matching team skill and show your current task before starting.

If your AI tool does not seem to know the team skills, say: "Read AGENTS.md and follow .agents/skills/team-onboard/SKILL.md."

A normal day

You say What happens
"What should I do today?" Your records are refreshed and you get the short daily view: tasks, one learning item, this week's hours, the next step.
"Start my task" The AI loads the task, its feature card and prototype, starts it and helps you build it.
"It works" The AI runs the real checks and records them. Then: "It's testing time." You test by hand and say what you saw.
(after your test passes) You push the branch and open a pull request. The reviewer checks it; the founder (or Niwesh for P2/P3 work of others) accepts it and the XP arrives.
"Pick something from the backlog" When your assigned work is done, you may take an extra task. Welcome, never expected.
"Teach me ..." Learn, explain it back, answer questions, save a short summary.
"Report a bug" A ticket with steps and a screenshot. The founder triages it.
"Done for today" Hours, handoff, encouragement from what you actually did; your records are committed on your branch and the pull request is opened or updated.

Commands such as /today or /closure are optional shortcuts if your tool supports them.

Engineers (Shankalpa, Umang, Anish)

  1. Ask for today. Start the top task.
  2. Build it in nepwalk-fe or nepwalk-be on a branch from the latest main, following that repository's AGENTS.md, CLAUDE.md and security rules.
  3. Run the repository's checks. Then test it yourself on a phone and a desktop.
  4. Push your branch and open the pull request. While you wait for the review: learning, or report what you found.
  5. Close the day.

Manager (Niwesh)

  1. Ask for today. Your tasks are tests, UX checks, bug reproduction and fix verification that Prakash assigns.
  2. Run the frontend and backend on your own computer (see day one), then test on real devices from the acceptance checks and the approved prototype.
  3. Every problem becomes a ticket with a cropped screenshot. Ideas beyond the task go to Prakash as tickets too.
  4. When you are a task's reviewer, record the review with what you checked.
  5. Accept finished P2 and P3 work from the others ("accept task X"). P0 and P1 stay with Prakash, and nobody accepts their own work.
  6. Before the daily standup, copy the standup report (copy icon next to "Warriors at a glance", or ask your AI tool "standup report") and paste it into the Slack channel.
  7. Follow the whole team in the dashboard's Team tab (or ask your AI tool "how is the team doing?"): every member's task and stage, hours by day, learning, last handoff, all tasks by stage and all tickets at once.
  8. Close the day.

Founder (Prakash)

  1. Ask for today: reviews, acceptances, blockers, new tickets, designs to approve and anyone with nothing assigned. The Team tab shows everyone at once.
  2. "Let's plan": milestones, feature cards, clickable prototypes you check on your phone, tasks with acceptance checks, and the backlog.
  3. Accept or reopen work. Merge the docs pull requests (team/<id> branches) one by one with the frontend and backend ones.
  4. Mark rest weeks for festivals or illness; adjust settings when needed.

The week

  • At least 15 hours of work and 5 hours of learning, Sunday to Saturday. Log them when you close each day.
  • More time is welcome and never asked for. Rest weeks pause the target.
  • Progress is the warriors' trek: XP for checked work, ranks and camps from Kathmandu to Everest, achievement badges and Unstoppable flames. Everest is paced for roughly a year of verified XP; there is no calendar lock. No rankings.

The dashboard (fallback)

Your AI tool does the daily work. The dashboard shows the same records when you want to look around: run node tools/team.mjs open in nepwalk-docs, or use the docs site, and claim your name once. You see Today, Work, Academy and My growth; the founder and manager also see Warriors. Work combines assigned tasks, an Inbox for reports, the optional Backlog and Completed tasks. The founder has no personal My growth tab.

In Chrome or Edge, Connect nepwalk-docs folder lets it save changes straight into your records. Other browsers show everything and give you the command for each change. See how records work.

When something is stuck

Problem What to do
"Choose your identity first" Say "onboard me".
doctor shows CHECK for the repository You may be offline, or still need access from Prakash.
The dashboard says the records are not loaded Run node tools/team.mjs open, or connect the folder.
Your pull request conflicts in docs/team/records Two people changed the same record. Ask your AI tool to merge main into your branch and keep both changes.
The AI says a test passed but you did not test Stop it. Only you record what you tested.

First terminal practice

Run these from nepwalk-docs, in any terminal:

pwd
git status --short
node tools/team.mjs today

Ask AI to explain the output. Do not copy commands blindly. Your first advanced lesson is Navigate and inspect safely. The tool's brand does not change the task, privacy, testing or review rules.

Verify the working environment

Complete the day-one readiness checklist for your role. It covers product setup, the manager's testing environment and a short AI workflow rehearsal. The docs doctor alone cannot verify those journeys.

Claim your identity once

Choose carefully at onboarding. The dashboard shows a fixed name, not an account selector. You can inspect other warriors' tasks, but their work controls are view-only unless you are the assigned reviewer or making a permitted founder decision. Everyone can still report tickets and manage their own learning.

Connect the docs folder to reconcile the browser claim with the CLI profile. A mismatch is refused, not silently switched. For an incorrect first selection, follow identity recovery with Prakash. Do not edit or delete task records to resolve identity issues.