enumerate-changes

To break down a scoped-need into single-commit changes, submit an approved scoped-need document to generate a flat, ordered list of discrete changes. Each item maps to one commit across all repository surfaces like cmd, internal, docs, web, cdk, contracts, and gov-infra.

The single-commit rule ensures each scoped-need translates into a discrete, standalone commit for clean rollbacks and clear provenance. This governance policy isolates changes across code, infrastructure, docs, and governance workflows into an ordered sequence ready for review.

To map infrastructure and code changes to a flat ordered list, apply a scoped-need transformation across all repository surfaces. This enforces test-first conventions and governance rubrics, producing a ready-to-commit plan where each surface maps to exactly one isolated commit.

Yes, generating a change list requires an approved scoped-need document as input. The skill processes this approved document to output a sequence of standalone commits that follow governance policies, documentation requirements, and test-first conventions for immediate integration.

Use a scoped-need transformation when you need to enforce single-commit discipline and test-first conventions across mixed repository surfaces like cdk, contracts, and gov-infra. It ensures every surface follows governance and isolation policies, producing a ready-to-commit plan for clear provenance.

Yes, enumerating changes from a scoped-need enforces test-first conventions alongside governance rubrics and documentation requirements. The transformation produces an ordered set of changes where each item is designed to be implemented as a single commit ready for review.