profession@di-atomic/delivery-manager · v0.1.0 · beta

The Delivery Manager owns your launch — every surface, from one card.

guild · delivery-manager@profession.md

Equip one role and it seeds the launch, renders the hero once, and ships blog, changelog, listing and marketplace — every surface voice-locked, and never a fabricated word. A bundle gives your agent tools. A profession gives it a job.

A delivery manager figure at a dark chalkboard, watching a single gold LAUNCH card connected to Plan, Build, Deploy and Test panels

For anyone who ships products, skills or client work — and loses a day to the “announce it everywhere” step that still comes out uneven.

Built by Di-Atomic Marketing & compliance agency Dogfooded on our own launches 7-language team Clients incl. ONYX Radiance, Pamit Group
16linked skills in the toolkit
4workflows it forks per launch
1hero render per launch — not three
0fabricated releases — ever

What this role owns

The Delivery Manager is staffed onto a project at its propagate stage. You don’t call it for one output — you put it in charge of the launch, and it coordinates the tool skills on one card. It splits the work by time horizon: a bounded launch (blog, changelog, listing, marketplace, docs) that is seeded, shipped and closed — and evergreen ops (social, SEO) it owns on a cadence and never finishes.

Verify the real release firstIt reads the actual diff before a word is written. Unknown delta → it stops and asks. Never fabricates.
Render the hero onceThe producer makes the hero; every other surface reuses it by URL. A second render is a defect.
Honor the publish gateNothing goes live while a launch’s gate is held. Consumers self-gate.
Close with a rollupThe card lands in Done with every live URL and a hero-render count of one.

The workflows it runs

skill-launch

The flagship. A skill lands in the Propagate column — it seeds the card, produces the blog and hero once, and every consumer surface reuses them.

product-release

A product version to the product’s own site: blog, changelog, docs, social. No marketplace, no listing.

client-campaign

A client deliverable to the client’s own tenant, where the report is the producer.

evergreen-cadence

The standing loop: social calendar and SEO upkeep, on a cadence, per brand — the surfaces that never finish.

The toolkit — sixteen skills, linked not copied

A profession links skills; it never copies them. Each stays independently owned and versioned, and each is a skill you can equip on its own. The profession is the composition that already knows the order. Every card links to that skill’s own marketplace listing.

Coordination & publishing · @opvs-ai
Live publishing · @spideriq
Surfaces & craft · @di-atomic

Equip it

Equipopvs profession equip @di-atomic/delivery-manager

In the first 30 days, put it in charge of your next launch and watch what it does with one card: the hero rendered once, every surface voice-locked, the publish gate honored, and — when it closes the card — a record of exactly what shipped and where it went live. You get a number you can optimize instead of a day you can’t get back.

Why this exists

I built this by dogfooding the same stack I run for clients.

delivery-manager is one role in the system behind Di-Atomic — the marketing & compliance agency that runs cognitoAI, SpiderIQ and OPVS. This very page, its blog post and its changelog entry were shipped by the profession’s own skill-launch workflow. It propagated itself. If you want launches that ship across every surface — in any of seven languages — that’s the day job. Let’s talk.

Book a 30-min call with Di-Atomic

Just want the role? Equip @di-atomic/delivery-manager free.