PROJ-AI — pour que vos projets ne s'arrêtent plus au livrable (Un repo, un agent, un IDE — pourquoi PROJ-AI ?)
Methodology article by Antoine HABERT (WEnvision) that formalizes **PROJ-AI**: a lightweight methodological layer so that collective projects become transferable rather than dying with their deliverable. Structuring triad: a **version-controlled git repo** (single source), an **AI agent** (Claude Code, Cursor) that reads the doctrine at every session, and a **markdown doctrine** specifying decision protocols and agent behaviors. Six directory zones (DOCS/, IDEAS/, DR/, OUT/, DOCTRINE/, AGENT/), operational **DPEV** cycle (Decide → Promise → Execute → Verify), Decision Records scored across 7 dimensions, dual interface (business Studio + tech CLI/IDE), five agent directives, and a shared **proj-ai-commons** library that bootstraps a project in 30 minutes vs. 1 week. Metrics across 3 engagements: onboarding **3 weeks → 2 days**, structural decisions tracked **30% → 100%**, architecture doc compilation **6 weeks → continuous**. Central aphorism: ***"The project is not a byproduct of the deliverable. The project IS the deliverable."*** Explicit stance: technology 20%, **team discipline 80%**.
Antoine HABERT (WEnvision — cabinet français de conseil en stratégie et IA agentique).