Release pack builder.

Collect the basic release facts, available assets, AI tool context, and human approval notes. The result is a `.md` file an agent can read before preparing distribution tasks.

01 What are we releasing?

Start with the plain facts an agent should not have to guess.

Track or project title Artist name Release type Release status

02 Why does this release exist?

Answer like you are explaining the song to a patient collaborator before touching any upload portal.

Listener intention

Best listener moment Release maturity

03 What can the pipeline use?

List only the assets that exist or have a known home. Unknowns can stay unknown.

Available assets Known links or locations Missing pieces

04 Where did tools help?

Keep the wording simple. This is context for provenance, metadata, and review, not a confession booth.

AI tools and assistance Human approval notes