Conciseness

Lean throughout: every line is a rule, an executable command, or a project-specific rationale (e.g., "Zero-downtime deploys require that existing rows satisfy the new schema immediately"), with no padding and no explanation of concepts Claude already knows.

Actionability

Fully executable guidance throughout: copy-paste commands (`npx prisma migrate deploy`, `npx prisma migrate status`, grep checks), safe/unsafe Prisma snippets, a red-flags list for generated SQL, and an expected output string ("All migrations have been applied.") covering the common cases.

Workflow Clarity

Deploy, rollback, and deprecation-removal flows are clearly sequenced with validation checkpoints (status confirmation with expected output, SQL inspection before commit, grep reference checks before DROP), but there is no explicit error-recovery branch when `migrate status` shows an unapplied or failed migration, keeping it just below the top anchor.

Progressive Disclosure

A single well-sectioned file with clear headers and no buried or nested references, and all content is genuinely needed during a migration review; however, at ~95 lines with no disclosure layering or split of secondary detail (e.g., credentials), it does not fully meet the top anchor.

Specificity

Lists several concrete actions — "reviewing a PR that touches the Prisma schema or migrations", "running migrations in staging or production", "auditing schema changes for safety" — but omits capabilities the body covers (rollback, incident response), so coverage has minor gaps rather than being comprehensive.

Completeness

The "when" is explicit with three concrete trigger clauses, but the "what" is conveyed only through the gerund actions inside the trigger list — there is no separate capability statement, so it falls just below the anchor requiring both clearly and explicitly.

Trigger Term Quality

Natural phrases users would say are present ("reviewing a PR", "Prisma schema", "migrations", "staging or production"), but common variations like "database", "deploy", or file-level terms such as "schema.prisma" are missing.

Distinctiveness Conflict Risk

"Prisma schema", "migrations", and "staging or production" carve out a clear niche with distinct triggers and minimal risk of firing for unrelated skills.