APEL (Agentic Product Engineering Lifecycle) is a proposed model for agent-assisted delivery. Work flows through five phases, with clear owners and evidence at each step.

THE FIVE PHASESFrom intent to a verified release
  1. DiscoverUnderstand the problemProduct
    OUTPUTEvidence and product intent
  2. RefineMake the target clearProduct · Engineering · QA
    OUTPUTSpecification and test intent
  3. BuildImplement and reviewEngineering
    OUTPUTReviewed change and evidence
  4. ValidateTest behavior and acceptanceQA · DevOps · Product
    OUTPUTValidation and acceptance evidence
  5. OperateDeploy, verify, and learnDevOps · QA
    OUTPUTVerified release and operational findings
Agents assist across the phases. People retain ownership of decisions and acceptance.

The working rules

  • Pull when ready. Product sets priority; engineers pull eligible work as capacity opens.
  • Specify before building. Carry the intended behavior and test approach into implementation.
  • Keep decisions owned. Agents assist; people approve changes, accept outcomes, and control releases.
  • Verify beyond the build. Test behavior, confirm product acceptance, and check the live release.
THE FEEDBACK PATHSEvidence determines the next move

Learn and adjust

Compare expected effort with actual effort. Track waiting, rework, and failures to identify what needs attention.

The source model uses on-demand staging and weekly production releases. Choose a cadence that fits operational needs; keep each item’s ownership and evidence visible.

Based on APEL’s September 2026 working draft. This is a proposed model, not a report of measured results.