ALPACA-template maps Waterfall QG1〜QG6 onto Agile checks

The write-up follows an earlier installment that covered AI Session Plan, Session Handoff and Integration Report as a way to keep AI conversation history from becoming the source of truth for work. This time the unit of discussion moves up a level, to the development process itself. The author's stated reason for unifying the two models is that "what must be verifiable" and "when and how much to build" are separate questions.

The template keeps common deliverables such as BRQ, FRQ and NRQ, and manages ID links from requirements through design and test under one convention. In Waterfall, QG1 through QG6 sit at each phase milestone; for example, QG1 checks success criteria for business requirements, inputs and outputs for functional requirements, objective verification conditions for non-functional requirements, and consistency of system boundaries and requirements. The author stresses that a document simply existing does not count as complete.

For Agile, applying the six gates as-is would mean passing phase gates six times per Sprint. The template instead reads them as an inception gate, PBI-level DoR/DoD, a release-candidate quality gate and an operational readiness review, and it treats PBI-level Done as distinct from the whole system being releasable. The author also notes a downside: updating version control, traceability, evidence and change records every Sprint raises the management burden even for minor improvements.