Conciseness

Lean operational prose that assumes Drizzle competence — no padded explanations of what Drizzle or migrations are, and every line states a rule, command, or invariant.

Actionability

Provides copy-paste-ready commands (pnpm db:generate, drizzle-kit generate --custom --name, pg_dump --schema-only, pnpm docker:reset) and concrete decision lists for auto vs. custom migrations covering the common cases.

Workflow Clarity

Numbered default workflow and a 7-step baseline-reset procedure with validation checkpoints ('Review against the schema dump', 'stop and assume drift until proven otherwise'); validation is present so the destructive-op cap does not apply, though error-recovery loops could be more explicit.

Progressive Disclosure

Single self-contained file with clear, well-ordered section headers and no nested references; appropriately organized, though slightly above the under-50-line simple-skill threshold.

Specificity

Lists multiple concrete actions — 'changing libs/database/src/schema.ts, adding Drizzle migrations, debugging drizzle-kit drift, or deciding between auto-generated and custom SQL migrations' — with comprehensive coverage of the migration niche.

Completeness

Explicit 'Use when ...' clause answers 'when' with concrete triggers, and the 'what' (migration authoring/triage) is clear, but the capability statement is distributed across triggers rather than led upfront.

Trigger Term Quality

Strong natural terms a Drizzle user would say ('Drizzle migrations', 'drizzle-kit drift', 'schema.ts') plus a concrete file path, but a few common synonyms or phrasings are absent.

Distinctiveness Conflict Risk

Highly specific to Drizzle migrations in this codebase, anchored by a file path and issue #867, giving a clear niche with minimal conflict risk.