Skip to content

Team learning

Learning prepares each member for upcoming NepWalk work and for working well with AI. Topics can be technical, AI, management or general business learning.

Where topics come from

  1. Founder-assigned: for everyone, or for chosen members. Everyone starts with AI foundations, which teaches our own setup: your AI workspace, clear context, one task to done, checking AI work and reporting bugs in the terminal, your records and branch, and learning by explaining.
  2. Member-created: discuss your goals and upcoming work with AI, then add a topic or a whole path for yourself ("teach me ...").

The founder assigns and reviews team learning but keeps personal learning outside this workspace. “Everyone” means the manager and engineers for learning and growth. Each participating member keeps their own record, even for a shared topic. Personal learning never changes product scope or work assignments.

Ask your AI tool "teach me" and it teaches from these pages. To read them yourself, open the .md files in your browser with a Markdown viewer extension (see getting started), or use the docs site.

The learning loop

  1. Read our guide first: the matching section of these docs ("Read the guide" in the dashboard).
  2. Learn with AI: copy the topic's prompt and paste it into your AI tool. It works only when the AI is opened inside your nepwalk-docs folder.
  3. Explain it back in your own words and answer the AI's follow-up questions.
  4. Close the gaps it finds, then explain again.
  5. The AI saves a brief summary of what you understand. You never record it yourself.

A topic is understood when you explained it and no gaps remain. Using it in real work is optional and never required to finish a topic; when you do, you can record it for a small XP bonus. Reading, or text the AI wrote, does not prove understanding.

Records

  • The team-learning skill records your explanation, the questions with your answers, open gaps and the summary. Each discussion is kept, so earlier understanding stays visible.
  • Learning hours count toward the weekly 5 hours and are logged at closure.
  • Each member's roadmap and summaries are in the dashboard's Academy (team dashboard) and in a terminal with node tools/team.mjs learning.

These are team-visible learning notes, not private chat transcripts. Leave out personal circumstances, credentials, customers and company financial or business details. General business and management concepts are welcome.

Courses and unlocks

Academy starts with AI foundations. Later courses are previews with a visible unlock condition; they cannot be started, reviewed or applied until prerequisites are understood. The same rule applies to the browser, terminal and AI tools. Each member unlocks courses independently. Reading, starting and logging hours do not count; every assigned prerequisite topic needs an understood or applied record. Practical use remains optional. If a later teach-back finds gaps, dependent courses lock again while earlier records, XP and badges remain preserved.

Course Audience Opens after
AI foundations Everyone Available first
AI fieldcraft Everyone AI foundations
Product foundations Everyone AI fieldcraft
AI engineering Engineers AI fieldcraft
Engineering essentials Engineers Product foundations + AI engineering
Reliable delivery Engineers Engineering essentials
AI quality and management Manager AI fieldcraft
Quality and UX Manager Product foundations + AI quality and management
Team leadership Manager Quality and UX

The AI practice guide covers fieldcraft and the role-specific AI courses. Product and delivery covers the later courses. Each topic includes an explanation, example, teach-back prompt, fresh scenario and optional exercise. Choose one topic at a time; the roadmap is preparation, not a new daily quota. The founder sees the full course catalogue and each member’s learning progress without receiving personal learning or XP.

Personal paths remain welcome. Paths outside this configured curriculum have no automatic prerequisite. The founder can configure course prerequisites through policy.update; see operations. Role-specific topics are assigned to the current roster. When onboarding another person, the founder should assign that role’s topics to them before expecting those courses to unlock. Course gates never block an assigned product task.