Content
85%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A strong, highly actionable checklist: concrete executable code, explicit decision tables, and validation checklists at the start and end. The two real defects are the broken references to a nonexistent reference/cosmos-config.md file and some inlined long-form content (the 80-line Option C example, Appendix B) that should live in that reference file.
Suggestions
Create the referenced reference/cosmos-config.md file (or fix the path to an existing references/ file) — all four in-body links to it currently dead-end.
Move the long Option C example (individual operators + S3 check, ~80 lines) and Appendix B's operational extras into the reference file, keeping a one-line pointer plus a minimal inline snippet per section.
Merge the two RenderConfig sections (§2 parsing strategy and §5 testing behavior) or cross-reference them so the config object is configured in one place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with decision tables and code and assumes Claude's competence ("Execute steps in order. Prefer the simplest configuration that meets the user's constraints"), with no re-explanation of known concepts. It sits at 4 rather than 5 because the ~80-line Option C example (S3 file checks, clone operator) and duplicated RenderConfig coverage in sections 2 and 5 could be trimmed. | 4 / 5 |
Actionability | Every section gives copy-paste-ready code with concrete arguments (ProjectConfig, DbtDag, DbtTaskGroup, operator_args dict) plus decision tables specifying required params and exact env vars (AIRFLOW__COSMOS__REMOTE_TARGET_PATH, DBT_DOCS_PROJECTS JSON). This matches the fully-executable anchor covering the common cases. | 5 / 5 |
Workflow Clarity | The workflow is explicitly ordered ("Execute steps in order", numbered sections 1-8) with validation checkpoints at both ends: an upfront "Before starting, confirm: (1)...(6)" checklist and a closing Safety Checks checklist. This matches the anchor requiring explicit validation steps and checklists for complex processes; no meaningful checkpoint gaps remain. | 5 / 5 |
Progressive Disclosure | References are clearly signaled and one level deep ("See [reference/cosmos-config.md](...#execution-modes-executionconfig)"), but the bundle contains no reference file at all — the four links to reference/cosmos-config.md point to a nonexistent path, and the detail that would live there is inlined in the body. Structure is good, but broken navigation fits anchor 3 rather than 4. | 3 / 5 |
Total | 17 / 20 Passed |