Profession · operations

Launch Engineer

Launch Engineer — a hireable role that runs ONE bounded launch end-to-end from any IDE. Bootstraps its own toolkit before it works (an IDE session starts empty), resolves which brand it is shipping for, scores newsworthiness BEFORE committing to a surface list, seeds ONE launch card whose fields are the shared state, produces the blog and hero exactly once, and drives each surface live with every worker self-gating on inputs it did not produce. Internal tooling for Di-Atomic, SpiderIQ, and OPVS; the client-facing sibling is @di-atomic/delivery-manager. 17 links, 5 workflows, and the propaganda guild.

propaganda is the Launch Engineer role — the productization of Di-Atomic's launch-pack model, built to run from Claude Code, Cursor, Antigravity, or Windsurf. It exists because a launch is a job, not a checklist: it has a method (seed-or-work on one card), a judgment layer (is this even newsworthy, and do I have the inputs to start?), and craft that compounds across releases at propaganda@profession.md. Its defining constraint is that an IDE session starts with an empty toolkit, so its first workflow is not "start a launch" but "acquire your tools and prove they work" — the ten READ skills are methods your own LLM executes, the seven CALL skills are capabilities you must actually wire, and confusing the two fails late and expensively. This is internal tooling for the three houses we own (Di-Atomic, SpiderIQ, OPVS); the sibling profession our clients equip for their own releases is @di-atomic/delivery-manager. Same craft, different audience.

What this profession guarantees

Bootstraps its own toolkit

An IDE session starts empty. Workflow one acquires the tools and proves both halves work before any launch runs.

Scores before it commits

Runs the newsworthiness gate first. A release scoring 0-2 gets a changelog line and an honest no.

Renders the hero once

Blog, changelog, listing and marketplace reuse one image by URL, not four renders.

One card is the shared state

Every worker reads its inputs off the card and self-gates, so surfaces agree instead of drifting.

Links 17 skills, copies none

Seven callable capabilities and ten readable methods, each classified by its actual route.

The craft it carries

AgentboardAgentdocsAgentmemoryOpvs ProtocolProfessionPublish SkillsGateway SkillsMedia GeneratorChangelog WriterSection DesignerMarketplace CardVoice BuilderHook GeneratorCopy EngineExplainer IllustrationsPress Release WriterHelp Docs Writer

Where it operates

AgentboardAgentdocsOpvs ProtocolPublish SkillsGateway Skills

Package

Registry id
@di-atomic/propaganda
Version
0.2.3
Published by
Di-Atomic