← ClaudeAtlas

implementlisted

Fill in the stub modules of a pipeline emitted by rote, so it actually runs. Use after `rote emit` or `rote compile` when the emitted app still has extracted/* stubs that raise a "[rote stub]" error or a bare NotImplementedError, or when the user says "implement the stubs", "fill in the extracted modules", "make the compiled pipeline run", "wire up the real API calls", or `rote run` fails on a stub. Reads each node's IR contract (inputs, declared output keys, constants, description, source section), writes real code that honors it, leaves rote-owned files alone, and verifies with `rote run`. Spends no compilation tokens.
trevhud/rote · ★ 8 · AI & Automation · score 74
Install: claude install-skill trevhud/rote
# Implement the stubs of an emitted pipeline `rote emit` and `rote compile` produce a runnable app whose deterministic steps are scaffolds: every `pure_function` and `external_call` node that has no real implementation yet gets a stub that fails on call. Your job is to replace those stubs with working code that honors each node's IR contract, then prove the pipeline runs end to end with `rote run`. You write code only in user-owned files. rote owns everything else and regenerates it on the next emit. The CLI ships on PyPI as `rote-cli`. Invoke it as `uvx --from rote-cli rote <args>`, which works on every release (the `uvx rote-cli` shorthand needs a release newer than 0.14.0). Running a Python app needs that runtime's extra in the same environment, because `rote run` executes it with its own interpreter: `uvx --from 'rote-cli[dbos]' rote run ...` for DBOS, `'rote-cli[temporal]'` for Temporal. If the user is inside a rote checkout with a `.venv`, `.venv/bin/rote` works too. ## 1. Locate the emitted dir and its IR The user names the directory, or it is the most recent `--out` in the conversation. Accept any of: - a `rote compile --out` dir: IR at `compiled/pipeline.yaml`, apps under `runtime/<target>/` (ask which target if there are several); - a bare emitted runtime dir. Find the runtime from its marker files, in this order: `wrangler.jsonc` = cloudflare, `src/inngest/` = inngest, `dbos-config.yaml` + `main.py` = dbos, `dbos-config.yaml` alone = dbos-ts, `workflow.py`