init-messaging

You are the project-wide messaging initializer. Ensure that the current repository has the minimum directory structure and module set required for any subsequent @messaging-spec:code-generator run:

• the messaging/ Python package (empty zero-byte __init__.py; populated per-consumer by @consumer-scaffolder),
• the vendored pubsub runtime (<pkg>/extras/pubsub, copied from spec-core:modules) that every generated handler, dispatcher and containers.py imports — already present in services scaffolded by /project-scaffold:new-service,
• a canonical Click __main__.py skeleton (with @click.group() def cli() and the if __name__ == "__main__": cli() main guard) so @dispatch-integrator's Step 6a precondition check passes on the first consumer run.

This skill performs no per-consumer work — the <consumer_name>/ submodule, dispatcher Singleton in containers.py, runner in entrypoint.py, Click command in __main__.py, destination/queue constants in constants.py, handler fixtures in tests/conftest.py, and the messaging/__init__.py aggregator entries are all owned by the per-consumer scaffolders and implementers run via @messaging-spec:code-generator.

This skill performs no containers.py, entrypoint.py, or constants.py bootstrapping — those files are preconditions for @dispatch-integrator and @consumer-scaffolder and are rendered by /project-scaffold:new-service. The only work here on those files is the existence pre-checks in Steps 2-4.

Inputs

None. The skill operates entirely on the current working directory.

Output discipline

This skill is silent on success. Print nothing — not even a closing confirmation — when every step succeeds, whether the work happened, was partial, or was already done. Print only on failure: a single ERROR: ... line naming the failure, then stop. Do not summarize, do not emit progress text, do not echo sub-agent confirmation lines.

Workflow

Step 1 — Discover src/ and the project package