Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-structured, source-routed overview with a clear phased workflow, strong security and validation checkpoints, and detail appropriately split into verified one-level-deep references; its main weakness is some repetition of the 'knowledge not code' framing and scope restatement.
Suggestions
Consolidate the 'knowledge over shipped code / no executable code' rationale, which currently appears in the intro, the principle line, and the frontmatter — state it once and reference it elsewhere.
Drop scope/out-of-scope restatements already covered by the frontmatter description to avoid duplication between the description and the body.
Trim the philosophical 'Do not look for a pyproject, a tools package, an orchestrator engine, or shipped scripts' sentence; the single principle line already conveys the same point.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is information-dense with migration-specific operational knowledge Claude does not already know, but repeats the 'knowledge over shipped code / no executable code' framing across the intro and principle line and restates scope already present in the frontmatter, so it is mostly efficient yet could be tightened rather than fully lean. | 2 / 3 |
Actionability | It gives concrete directives — apply conversion-rules.md directly, prefer WRITE_NOS + teradatasql, pin exact dependency versions, stage in encrypted S3, load via COPY IAM_ROLE, scope the role policy to the staging prefix with aws:SourceAccount/aws:SourceArn/sts:ExternalId, enable CloudTrail and audit logging — so per the instruction-only carve-out the absence of shipped code is not penalized. | 3 / 3 |
Workflow Clarity | Six ordered phases each feeding result/ to the next, a dedicated Validation phase, restartable data migration, a state.md progress cursor, and a non-production checkpoint with 'never point write-path at production without explicit operator confirmation' form a clear sequence with explicit validation, so it is not capped at 2. | 3 / 3 |
Progressive Disclosure | An organized overview body points to 13 one-level-deep reference files (all verified present in references/teradata/) via a labeled References table, with no nested references, matching the clear-overview-with-well-signaled-references anchor. | 3 / 3 |
Total | 11 / 12 Passed |