Build something that is not there yet
Schedule dlt and dbt on DuckDB or MotherDuck without standing up an orchestrator
- When the only scheduler for a DuckDB or MotherDuck project is a cron entry on someone's laptop.
- When a load and a build need to run in order on a cadence and standing up a full orchestrator is out of proportion to the project.
Schedule a dlt load followed by a dbt build on DuckDB or MotherDuck using GitHub Actions or a MotherDuck Flight, with failure notification and per-run evidence kept in the repository. Covers the schedule and its evidence, not a general-purpose orchestrator.
Sample This Recipe has not been materialized in the Cookbook repository yet. Its trigger, description, prompt, agent guidance and acceptance conditions, and the explanation below, are prototype drafts. Its name, job, area and readiness come from the reconciled Cookbook seed snapshot. Readiness is a separate question from this one: it says whether the capability exists, not whether the writing has been reviewed.
Review planned Recipe
At least one capability or object type this Recipe needs is not supported yet.
Read the VibeData Recipe `motherduck-duckdb-scheduling` at https://getvibedata.ai/cookbook/motherduck-duckdb-scheduling At least one capability or object type this Recipe needs is not supported yet. Treat it as a reference, not as work to execute.
Recipe id motherduck-duckdb-scheduling · Not yet materialized in the Cookbook repository, so the pointer addresses this page.
Verified by
What has to be observably true before this Recipe is finished.
- a scheduled run completes the load and the build in order
- per-run evidence is committed to the repository
- a failed run sends a notification to the agreed channel
- no workflow file is hand-rolled outside the agreed schedule definition
Recipe promptThe task specification the agent reads. Reference only — it is not what you copy.
Deliver: Schedule dlt and dbt on DuckDB or MotherDuck without standing up an orchestrator. Schedule a dlt load followed by a dbt build on DuckDB or MotherDuck using GitHub Actions or a MotherDuck Flight, with failure notification and per-run evidence kept in the repository. Covers the schedule and its evidence, not a general-purpose orchestrator. Execute inside the current Intent. Its Domain, repository, platform, environment and attached sources are the context for this work — read them rather than asking for them. The work is done when: - a scheduled run completes the load and the build in order - per-run evidence is committed to the repository - a failed run sends a notification to the agreed channel - no workflow file is hand-rolled outside the agreed schedule definition Report the evidence for each condition above with the result. A condition you cannot meet is something to say, not something to work around.
Agent guidanceHow the agent approaches the work, and what it will not do.
Profile the inputs the grain, joins and measures actually depend on before proposing a model. Put the design up for review — grain first — then build in an isolated copy with tests and documentation landing beside the model rather than after it.
Composes
- job scheduling and run evidence
- dlt in the project
- dbt in the project
- GitHub Actions in the project
- isolated-copy execution and gate verification
Guardrails
- Build in an isolated copy. Production is read, never written.
- At least one capability this Recipe needs is not supported yet. Say so and stop rather than substituting a different approach.
What you need
- MotherDuck, or DuckDB.
- The jobs you want sequenced, and somewhere they are allowed to run.
- dlt and dbt and GitHub Actions in the project, or the intent to add it.
How it goes
- State the outcome in one sentence, in the language the request arrived in.
- Let it profile the inputs the grain, the joins and the measures actually depend on.
- Review the design. Disagreeing about grain here costs a sentence; after the model exists it costs a rewrite.
- Let it build in an isolated copy, with the tests and the documentation landing beside the model rather than after it.
- Read the acceptance conditions against the run.
What you end up with
The deliverable, in your own repository, as orchestration work a reviewer who knows the project reads as native to it. Alongside it, the evidence for every one of the acceptance conditions above — which is the part that is still there in three weeks when somebody asks.