Use after scope-need and relevant specialist skills approve work. Takes the scoped-need document and produces a flat, ordered list of discrete changes required. Each change is scoped to be a single commit.
A scoped need describes what is being delivered. An enumerated change list describes what must move in the repo. This skill is the transformation.
host's change lists vary: a narrow bug fix might be two to three commits; a new verifier addition might be four to six; a provisioning-flow refinement with managed-update recovery might be eight to twelve; a soul-registry on-chain contract addition with Safe-ready governance coordination is larger. The single-commit rule holds regardless.
An approved scoped-need document from scope-need. Specialist-skill findings (from maintain-governance-rubric, provision-managed-instance, evolve-soul-registry, audit-trust-and-safety, coordinate-framework-feedback, review-advisor-brief) if applicable. Load prior context with memory_recent.
Walk the scoped need against every surface of host:
cmd/<lambda>/ — Lambda entrypoints (control-plane-api, trust-api, email-ingress, provision-worker, render-worker, ai-worker, comm-worker, soul-reputation-worker)internal/controlplane/ — operators, portal, provisioning, billing, tipsinternal/trust/ — attestations, previews, instance authinternal/store/ — TableTheory models (DynamoDB)internal/secrets/ — SSM Parameter Store readsinternal/soul*/ — soul-registry subsystems (registration, avatars, reputation, local identity resolution, search)internal/<other-domain-package>/ — ~33 total domain packagescdk/ — AWS CDK (TypeScript)web/ — Svelte 5 SPAcontracts/ — Solidity + Hardhatdocs/ — ~40 markdown files (managed-instance-provisioning, attestations, lesser-release-contract, lesser-body-release-contract, adr/, deployments/, contracts/, roadmaps, recovery runbooks)scripts/ — build_release_assets.sh, generate-mint-signer-key.sh, managed-release-certification/*, managed-release-readiness/*, soul-backfill scriptsgov-infra/ — verifiers, evidence, pack.json, planning (threat model, controls matrix, etc.), AGENTS.md, README.mdgo.mod / go.sum — Go dependency changesweb/package.json / web/pnpm-lock.yaml (or equivalent) — frontend dependenciescontracts/package.json — Hardhat / Solidity dependenciesapp-theory/app.json — AppTheory deployment contractAGENTS.md — repository guidelines. Rarely touched; governance-level.README.md — top-level overview.CONTRIBUTING.md — contributor quickstart.A change that touches none of these isn't really a change.
web/ changes land separately. The SPA has its own build and CSP story.gov-infra/pack.json changes are governance events in their own commits with documentation explaining the rubric shift.coordinate-framework-feedback.Every enumerated item must answer: is this host-mission work, or scope growth outside?
If any item is scope growth, stop and revisit scope-need.
Every enumerated item must also answer: does this touch the gov-infra rubric (verifiers, evidence policy, pack.json)?
maintain-governance-rubric findings referenced.maintain-governance-rubric walk is mandatory.Every enumerated item must also answer: does this touch the multi-tenant boundary?
Every enumerated item must also answer: does this touch Solidity contracts, on-chain-reaching Go code, or Safe-ready governance payloads?
Every enumerated item must also answer: does this touch the release-verification pipeline (scripts, certification, readiness checks)?
provision-managed-instance walk.Every enumerated item must also answer: does this touch the trust API, instance-auth, attestations, or CSP?
audit-trust-and-safety findings.Every enumerated item must also answer: does this consume AppTheory / TableTheory / FaceTheory idiomatically?
coordinate-framework-feedback.Each enumerated item fits in one commit:
go build ./... succeedsgo test ./... passesgo vet ./... passesgofmt -l . emptycdk synth --context stage=lab succeedsweb/: lint + build clean; CSP validation passescontracts/: hardhat test passes; Slither clean; solhint cleangov-infra/: verifiers pass (including this commit's scope); evidence emits### N. <imperative title>
- **Paths**: <files or directories touched>
- **Surface**: <cmd / internal/<pkg> / cdk / web / contracts / gov-infra / scripts / docs / deps>
- **Classification**: <security / tenant-isolation / on-chain-integrity / governance / provisioning / managed-update / soul-registry / trust-API / CSP / operational-reliability / AGPL / framework-feedback / bug-fix / test-coverage / dependency-maintenance / docs>
- **Governance-rubric impact**: <none / additive / modifies — refuse if loosens silently>
- **Multi-tenant-isolation impact**: <none — default; traverses — refuse without authorization>
- **On-chain impact**: <none / off-chain only / Solidity — Slither + hardhat + solhint run / Safe-ready governance required>
- **Trust-API / CSP / instance-auth impact**: <none / preserves / tightens — refuse if loosens>
- **Consumer-release-verification impact**: <none / touches verification pipeline — elevated scrutiny>
- **Framework consumption**: <idiomatic / reported upstream>
- **Acceptance**: <one sentence: what makes this commit done>
- **Validation**: <`go test ./...`, `go vet ./...`, `gofmt -l .`, `cdk synth`, `hardhat test`, Slither, solhint, gov-infra verifiers, web build + CSP check>
- **Conventional Commit subject**: `<type(scope): subject>`
coordinate-framework-feedback, not patched locallygov-infra/pack.json changes in isolated commits with documentationweb/ changes isolated; CSP validation runsAppend only if enumeration surfaces something unusual — a verifier interaction subtlety, an on-chain ordering gotcha, a provisioning coordination detail, a CSP edge case, a framework-consumption pattern worth reporting. Routine enumerations aren't memory material. Five meaningful entries beat fifty log-shaped ones.
Invoke plan-roadmap to sequence the flat list into phases and identify the rollout plan across stages and (where applicable) on-chain networks.