# meppiel-getting-started-agentic-sdlc-enterprise-2026-10-01

## Veille

LinkedIn post by **Daniel Meppiel** (works with enterprise engineering teams at **Microsoft** and **GitHub**), dated **October 1, 2026**, accompanied by an infographic (~350 words). He proposes a four-entry-point decision framework for starting an **Agentic SDLC** at enterprise scale, with the right starting point depending on what already works, what is missing, and the organization's capacity to take on maintenance.

## Titre Article

Getting started with Agentic SDLC at enterprise scale (post LinkedIn et infographie)

## Date

2026-10-01

## URL

https://www.linkedin.com/posts/danielmeppiel_in-my-work-at-microsoft-and-github-with-enterprise-share-7511397522762883073-6Mhi/

## Keywords

Agentic SDLC, Agentic SDLC, skills, agent package manager, APM, HVE Core, Copilot Code Review, Coding Agent, Enterprise Managed Plugins, plugin registry, governed catalog, golden path, supply chain, pinned versions, Software Factory, GitHub Copilot, Microsoft

## Authors

Daniel Meppiel — travaille avec des équipes d'ingénierie d'entreprise chez Microsoft et GitHub ; post LinkedIn.

## Ton

Profile: practitioner account, framed as a numbered decision framework with short imperatives, aimed at enterprise engineering and architecture leaders. The text opens with his position ("in my work at Microsoft and GitHub with enterprise engineering teams") and sets a rule of choice: start from the gap you have and what your resources let you handle. The order of the four steps runs from least costly (activating what already exists) to most structuring (governing a catalog). The products cited are Microsoft's and GitHub's, which the context of the statement makes legible. The post grounds its reasoning in a claim of principle, that skills carry an organization's own expertise that no frontier model can guess, and closes with three brief injunctions.

## Pense-betes

- **The framework is not a mandatory sequence**: four entry points, to be chosen based on what already works, what is missing, and the organization's capacity to own maintenance. The infographic concludes: *"Start where your organization is today. Build on the earlier foundations as you scale."*
- **Step 1, native foundation**: Copilot Code Review (reviews enabled centrally across repositories), Coding Agent, and Enterprise Managed Plugins (approved plugins and shared skills rolled out without individual installation on supported clients). Little to no custom engineering.
- **Step 2, practices**: HVE Core is presented as an open-source, extensible Microsoft toolkit of practices, agents, and skills, to be studied and adapted rather than reinvented. Loop shown: Research → Plan → Implement → Review.
- **Step 3, skills as software**: when skills proliferate across teams, use software packages rather than copied files. APM (open source) makes it possible to create, validate, and compose packages, control sources, pin versions, and audit dependencies.
- **Step 4, governed catalog**: owners, approval, updates, and retirement for shared skills and plugins; definition of a "golden path" for the Agentic SDLC. Microsoft Copilot plugin registry is used to publish and govern plugins for Microsoft 365; GitHub Copilot support is noted as planned.
- **Why skills**: reusable instructions and resources that capture engineering and organizational expertise; the author writes that no frontier model can infer an organization's own way of working "unless you want to break the bank each time."
- ⚠️ **Scope**: a positioning post with no quantitative data or customer case; it does not say how many teams have followed this path. The author ties it all to enterprise-scale "Agentic Software Factories."

## RésuméDe400mots

Daniel Meppiel, who advises enterprise engineering teams at Microsoft and GitHub, published a decision framework on October 1, 2026 for starting an Agentic SDLC. He distinguishes four entry points, with the right one depending on what already works, what is missing, and the organization's capacity to own the topic. The goal is to build durable capability while delivering a fast return on investment.

First entry point: activate the native foundation. Copilot Code Review, Coding Agent, and Enterprise Managed Plugins bring shared capabilities to the whole enterprise with little to no custom engineering. The infographic specifies that reviews are enabled centrally across repositories and that approved plugins and shared skills roll out without individual installation on supported clients.

Second entry point: build up practices. HVE Core, Microsoft's open-source toolkit, offers engineering practices, agents, and skills, with a Research, Plan, Implement, Review loop. The idea is to draw on it and adapt it rather than inventing every workflow from scratch.

Third entry point: treat skills as software. As expertise in AI-assisted SDLC spreads and skills proliferate, the author recommends packages rather than copied files, with rigor in writing, packaging, versioning, and the supply chain. APM, an open-source agent package manager, makes it possible to create, validate, and compose packages, control sources, pin versions, and audit dependencies.

Fourth entry point: govern a catalog. Shared skills and plugins get owners, approval and lifecycle rules, up to retirement, and the organization defines its "golden path." Microsoft Copilot plugin registry, which publishes and governs plugins for Microsoft 365, is one option; GitHub Copilot support is noted as planned.

Skills are presented as the central building block: reusable instructions and resources that encode engineering and organizational expertise. No frontier model can infer this way of working, short of committing a considerable budget each time. Meppiel sees this as part of the foundation of enterprise-scale "Agentic Software Factories," and of any agent beyond the SDLC. His rule of thumb comes down to three sentences: start from the gap you have and what your resources let you handle, keep what works, add what you can maintain.

## GrapheDeConnaissance

- Daniel Meppiel —travaille_chez→ Microsoft (ORGANISATION, 0.9)
- Daniel Meppiel —recommande→ démarrer l'Agentic SDLC par l'écart existant et la capacité de maintenance de l'organisation (AFFIRMATION, 0.93)
- Agentic SDLC —utilise→ Copilot Code Review (TECHNOLOGIE, 0.9)
- Agentic SDLC —utilise→ Enterprise Managed Plugins (TECHNOLOGIE, 0.9)
- Copilot Code Review —fait_partie_de→ GitHub Copilot (TECHNOLOGIE, 0.88)
- Microsoft —publie→ HVE Core (TECHNOLOGIE, 0.92)
- Microsoft —publie→ APM (TECHNOLOGIE, 0.92)
- HVE Core —permet→ pratiques, agents et skills de SDLC à adapter (AFFIRMATION, 0.9)
- APM —permet→ contrôle des sources, versions épinglées et audit des dépendances de skills (AFFIRMATION, 0.93)
- APM —résout→ fichiers copiés entre équipes (CONCEPT, 0.85)
- Microsoft Copilot plugin registry —permet→ publication et gouvernance de plugins pour Microsoft 365 (AFFIRMATION, 0.92)
- Daniel Meppiel —affirme_que→ aucun modèle de pointe ne peut deviner la façon de travailler d'une organisation (AFFIRMATION, 0.85)
- Daniel Meppiel —affirme_que→ les skills sont la fondation des Software Factories agentiques à l'échelle de l'entreprise (AFFIRMATION, 0.85)
- Software Factory —utilise→ skills (TECHNOLOGIE, 0.8)

---
Canonical: https://www.thekb.eu/en/fiches/meppiel-getting-started-agentic-sdlc-enterprise-2026-10-01/