Global Onboarding — Projeto EITB
title: "EITB - STD-GEN Onboarding"
project: PRJ-EITB
author: Expert PMO Orchestrator (Nexus AI)
date: 2026-03-15
stage: PMO Governance
STD-GEN Onboarding
Global Onboarding: Project EITB
Welcome to Project EITB. This document contains the fundamental guidelines, the official file naming conventions, the project folder structure, and suggested prompts for working optimally with the AI (Nexus) within the project.
1. Naming Conventions & Standards
To ensure traceability, all generated functional documents must follow this structure:
[GROUP]-[TYPE]-[ID]_[descriptive_title].md
Example: PRJ-ARC-001_tobe_integration_flow.md
Global Example: PRJ-PLN-001_onboarding.md
1.1. Code Breakdown
[GROUP] — Document Group
| Code | Description |
|---|---|
| {project} | Global Project Management documentation (applies to the entire project). |
| (add more group codes here as defined for this project) |
Note: Add project-specific group codes (e.g.
PLAN,TX,CRM, etc.) as they are defined during Sprint 0.
[TYPE] — Document Type
| Code | Description | Template |
|---|---|---|
GEN |
General Documents. | NXS-GEN_General.md |
UCD |
Use Case Document. | NXS-UCD_UseCase.md |
ARC |
Architecture / Flow Diagram. | NXS-ARC_Architecture.md |
DOC |
Document (formal deliverable for the client or other external entities). | NXS-DOC_ClientDocument.md · NXS-DOC_StatusReport.md |
PLN |
Execution Plan / Onboarding. | NXS-PLN_ExecutionPlan.md |
AGN |
Agenda / Script — pre-meeting document (topics, goals, attendees). Required before every meeting. Format: [GROUP]-[YYYY-MM-DD]-AGN_[theme].md |
NXS-AGN_Agenda.md |
ACT |
Minutes / Act — post-meeting document (decisions, action items, owners). Required after every meeting. Format: [GROUP]-[YYYY-MM-DD]-ACT_[theme].md |
NXS-ACT_Minutes.md |
REQ |
Requirements (Business Requirements). | NXS-REQ_RiskRegister.md |
CHM |
Change Management. | NXS-CHM_ChangeManagement.md |
SCH |
Schedule / Planning. | NXS-SCH_Schedule.md |
MAT |
Material / Presentation. | NXS-MAT_Material.md |
PRS |
Deck / Executive Presentation. | NXS-PRS_ExecutiveDeck.md |
EPC |
Epic / Task Definition (Agile backlog item or task specification). | NXS-EPC_Epic.md |
PULSE |
Daily RAG Pulse report (auto-generated — do not create manually). | NXS-PULSE_DailyPulse.md |
Meeting naming note: AGN and ACT place the date before the type so that files sort chronologically in any file explorer. Both documents for the same meeting share the same date and theme, making them easy to locate together (e.g.
PRJ-2026-03-11-AGN_kickoff.mdandPRJ-2026-03-11-ACT_kickoff.md).
[ID]
Three-digit sequential number (001, 002, …).
1.2. Nexus Control Block (Mandatory)
All documents must include the Nexus Control Block at the very beginning of the file, composed of:
- HTML Header (table with project code on the left, status badge in the centre, and document type label on the right).
- Approval Workflow table (roles, names, status, and date). (Required for all types except meeting minutes —
ACT.) - Revision History table (version, date, author, description).
2. Project Directory Structure
Project {PROJECT} follows the official Nexus standard for Admin-profile projects. All folders are located under PRJ-{project}/ and are organized as follows:
PRJ-EITB-NXS/
├── a-nexus/ # Project AI Agents and Workflows
├── b-management/ # Project Management, Strategy, Governance, Architecture
│ ├── 0-governance/
│ ├── 1-kickoff/
│ ├── 2-AsIs/
│ └── 3-ToBe/
├── c-meetings/ # Meeting minutes (Dailies, Plannings, Retros, Client)
├── d-documents/ # Documents produced for customer (deliverables)
└── f-workspace/ # Technical and functional execution space2.1. Key Folder Descriptions
| Folder | Purpose |
|---|---|
a-nexus/ |
Contains project-specific specialist AI agents (agents/), workflows (workflows/), and auto-generated daily Pulse reports (pulses/). |
b-management/ |
Strategic project management documentation, Governance rules, As-Is audits, and To-Be architecture master plans. |
c-meetings/ |
Centralised repository for meeting scripts (AGN) and minutes (ACT) with EITB and Internal teams. |
d-documents/ |
Formal documents and deliverables produced for the client with commitment force. |
f-workspace/ |
Functional execution space containing work-in-progress, training details, kickoff materials, and deliverables mapped to agile phases. |
Control de Documento (Document Control)
A. Historial de Revisiones
| Versión | Fecha | Autor | Motivo del Cambio |
|---|---|---|---|
| v1.0 | 2026-03-15 | Expert PMO (Nexus AI) | Migración a estándar de documentación PMO EITB. |
B. Matriz de Aprobación (Sign-off)
| Acción | Rol / Área | Nombre | Estado | Fecha |
|---|---|---|---|---|
| Elaboró | Project Management (PMO) | Nexus Core AI | Firmado | 2026-03-15 |
| Aprobó | Owner Proyecto | Project Owner | Firmado | 2026-03-17 |
Documento generado bajo el estándar de Gobernanza Nexus Framework.
Nivel de Confidencialidad: INTERNO STRICTO - EITB / INETUM.