Skip to content

Team workflow

How the NepWalk team works, agreed on 22 October 2026 (decisions A16, A17, A18). For setup see getting started; for the record commands see how records work.

Roles and workspace

Everyone works from nepwalk-docs, through their AI tool in a terminal (A22): they paste screenshots and ask in plain words, and the AI records everything. The dashboard is the fallback. The team are warriors (A23). Engineers also need sibling nepwalk-fe and nepwalk-be repositories. The manager may use docs alone with an app preview.

  • Founder: plans milestones and features, approves designs on a phone, assigns all work and sets priorities, accepts results, merges and releases.
  • Manager: does assigned testing, UX checks, bug reproduction, improvement analysis and fix verification; reviews when named reviewer; follows the whole team's progress and all tickets in the Team view (A20); accepts P2/P3 work and tests on a local frontend and backend (A24). Does not assign work.
  • Engineer: builds the assigned scope, verifies it and prepares the handoff.

Anyone can report a bug or idea with screenshots. Reports wait for the founder's triage. A report is not permission to build it.

The week

  • Each member gives at least 15 hours of work and 5 hours of learning a week, Sunday to Saturday, Kathmandu time, logged at the daily closure.
  • More time is welcome and never asked for. Hours earn no XP.
  • The founder marks rest weeks for festivals, illness or exams; they have no target.
  • Progress is the warriors' trek: XP for checked work, ranks, camps, badges and streaks, shared with the whole team. Ranks are titles, never league places.
  • Friday: the founder's weekly review.

Today

Plain language works: "what should I do today?". The answer stays short:

Today's tasks:
- Complete header and footer design (P0)
- Upgrade landing page (P1)

Learning:
- How AI skills work

This week: 9/15 h work · 3/5 h learning
Trek: Lukla · 45 XP · badges: 👣 🔨 💡

Next: Start Complete header and footer design (header-footer).

Only the team records assign work. Old dates in tasks.md are history.

Planning (founder)

  1. Discuss the outcome; record new decisions in the decision log first.
  2. Milestone, then a feature card with acceptance checks.
  3. A clickable HTML prototype for any screen change (D8), checked by the founder on a phone before approval. Visuals in SVG only.
  4. Tasks with a clear brief, acceptance checks, an assignee or the backlog, an independent reviewer, a priority, a kind and a size in XP.
  5. Plan about a week of work per person; a slight stretch is good.

One task to completion

  1. Load the task, its feature card and its approved prototype, then its spec.
  2. Start it. A task with unmet dependencies or an unapproved design cannot start.
  3. Build it, test first: API contract, database, backend, then frontend. Unit and integration tests are both required. Run the code repository's real automated checks and record them.
  4. AI user test: the AI uses the change on local dev like a real user and like an attacker. It fixes what is in scope or related and small, and files tickets, with a suggested priority, for the rest.
  5. "It's testing time": a person tests it by hand and records what they saw. Failures go back to building.
  6. Security check and self-review, then push the task branch and open a pull request into stage. The independent reviewer approves or requests changes.
  7. The founder accepts it, which awards the XP, or reopens it.

One active task per person, counting testing and waiting for review. While waiting, learn or report bugs. Browser automation runs only in the AI user test or when a person asks for it, and never replaces the manual test.

Backlog, blockers and extra work

  • When nothing assigned can start, a member may pick a backlog task open to their role. It follows every gate above and counts as extra work. Returning it is fine.
  • A blocker records what blocks you, what you tried and who decides. The founder unblocks, reassigns or pauses.
  • Findings outside the task's scope become tickets for the founder.

Closure

"Done for today" logs the day's work and learning hours and records:

  • completed and accepted work, and work handed to a reviewer;
  • learning and its summary;
  • extra work;
  • blockers and unfinished work, kept open;
  • the next step.

Encouragement names real evidence. Then the records are committed on the member's team/<id> docs branch and the pull request is opened or updated. The next session starts from that handoff.

Shared records and privacy

Tasks, tickets, screenshots, designs, learning and hours are files in docs/team/records/, one per record. They travel with normal docs pull requests and are visible to the whole team; the docs site is behind Cloudflare Access. Private business work, money, customers and credentials still never go in them.