Skip to content

NepWalk v1

Keep new product work here. Existing MVP documents remain at their current paths. Create subfolders as work needs them:

  • features/: feature descriptions, user journeys and acceptance checks.
  • designs/: HTML designs and mobile, tablet and web review views.
  • tasks/: detailed task specifications linked to their feature and design. Start from tasks/TEMPLATE.md; the team-spec skill fills it.

When assigning a task, link the relevant v1 feature, design and specification. Live task/ticket records continue using the existing team tools and storage. Future product versions can use sibling folders such as docs/v2/.

Branch flow

In frontend, backend and docs: task branches merge into stage first. Everyone merges their own pull requests into stage. Niwesh tests stage locally and opens the release pull request stage into main; Prakash reviews and merges it (A28). Only main deploys and is visible (A27).