> ## Documentation Index
> Fetch the complete documentation index at: https://ihub.learnille.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agile Workflow & Engineering Development Rituals

> Migrated from the previous Learnille internal documentation hub

## Overview

Learnille engineering operates on a **2-week sprint cycle** focused on delivering high-quality, tested feature increments.

***

## 🔄 1. Sprint Cadence & Ceremonies

```
+-------------------------------------------------------------------------------+
|                             2-WEEK SPRINT CADENCE                             |
+-------------------+-------------------+-------------------+-------------------+
| Day 1 (Monday)    | Daily (Mon-Fri)   | Day 9 (Thursday)  | Day 10 (Friday)   |
+-------------------+-------------------+-------------------+-------------------+
| Sprint Planning & | Standup (15m):    | Backlog Grooming  | Sprint Demo &     |
| Goal Alignment    | - Yesterday       | & Story Pointing  | Retrospective     |
|                   | - Today / Blockers|                   |                   |
+-------------------+-------------------+-------------------+-------------------+
```

***

## 🛠 2. Git Branching & Pull Request (PR) Workflow

* **Branch Naming**: `feature/feature-name`, `fix/bug-name`, `refactor/scope`.
* **Package Independence**: Always remember each package (`server`, `admin`, `instructor`, `student`) is an independent codebase. Do not cross-import types across packages.
* **PR Review Checklist**:
  1. All new NestJS endpoints protected by `JwtAuthGuard` and DTO validation.
  2. No hardcoded secrets or API keys.
  3. Real E2E tests added for critical user journeys (following zero-mocking playbook).
  4. Unit test suite passes cleanly.
  5. UI components adhere to visual guidelines (no default Inter/Arial fonts, clean CSS variables).

***

## ✅ 3. Definition of Done (DoD)

A user story or task is considered **Done** when:

* Code is merged into `main` after passing peer code review.
* Automated CI build and test suite pass cleanly.
* End-to-end verification has been performed in dev/staging.
* Swagger API documentation and relevant space docs in `documentation/` are updated.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.