LeaveTrack
A complete, real artifact chain the Dev Track runs nexus-dev-toolkit against.
A small, complete artifact chain for the Dev Track to run nexus-dev-toolkit against — not the core program's LMS/Meridian demo, but LeaveTrack, one of the core program's own sample-project-library picks ("the safest first pick," per Module 1), sized down to exactly what a developer needs to exercise /scaffold and the EPAV cycle.
The Chain
Each document below is rendered for reading here, with a link to the raw file underneath it for copying into a real project's docs/ folder.
| Document | Traces | Used in |
|---|---|---|
| BRD — 7 requirements (BR-01..07) | — | Dev 1 (what /scaffold reads) |
| PRD — 8 user stories (US-01..08) | Each story → a BR | Dev 1 |
| Architecture Document + ADR-E001 | Components → PRD stories | Dev 1 (ADR-E001 is why Day 0 uses a mock cookie session) |
| Dev Tasks — 9 atomic tasks (TASK-010..018) | Each task → a US, an epic | Dev 2 (TASK-014) and Dev 5 (TASK-011) |
How to Use It
mkdir leavetrack && cd leavetrack nexus init . mkdir -p docs # copy the raw files linked from each page above into docs/, # matching the same brd/ prd/ arch-docs/ dev-tasks/ layout /scaffold # Day 0 — see Dev 1 /evaluate TASK-011 # Day 1 — see Dev 2 onward
No Figma export included
This sample project is for exercising the EPAV cycle (Dev 2–8), not the Day 0 design-fidelity checks in /scaffold's VALIDATE step. Running /scaffold against it will skip or skip-and-flag the UI-shell/Figma-matching checks — that's expected.
Two Tasks Used as Concrete Examples Elsewhere
- TASK-014 (approve/reject decision endpoint + audit record) — the full
/evaluate → /plan → /apply → /validatewalkthrough in Dev 2 — The EPAV Workflow - TASK-011 (submit leave request form + API) — the reviewer-skill example in Dev 5 — AI-Assisted Dev with /apply
You don't have to use these two — any row in the Dev Tasks CSV runs through the same four commands.