Conciseness

The body is dense with project-specific, non-inferable knowledge (CI guard names, lock semantics, helper classes) and assumes Django competence — no padding like explaining what a migration is. A few passages could be tightened, e.g., the long prose on SafeDropTable deadlock mechanics and Django default= behavior partly re-states what an experienced model knows, which fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean score-5 anchor.

Actionability

Guidance is copy-paste ready throughout: exact commands ('DEBUG=1 ./manage.py makemigrations', './manage.py sqlmigrate <app> <migration_number>', the 'rg -n "INSERT INTO <table>|insertRow…"' grep), named helper operations (SafeAddIndexConcurrently, DropColumnConstraints, untrack_field), and complete executable code blocks for callable choices and db_default. This matches 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

Workflow Clarity

The Workflow section gives a clear classify → generate → apply safety rules → validate sequence, destructive operations carry explicit validation (sqlmigrate checks, 'confirm ./manage.py makemigrations --dry-run reports no state drift', audit_orphan_hot_table_fks, deploy-cycle waits), so the destructive-operations cap of 3 does not apply. It sits below the score-5 anchor because explicit error-recovery feedback loops ('if validation fails, do X') are mostly implicit — e.g., what to do when sqlmigrate shows a stray DROP DEFAULT is left to inference.

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and external material is deferred one level deep to clearly signaled repo docs with pinpointed sections — 'Read these files first' lists four docs with exact headings, and repeated pointers like 'Full guide: safe-django-migrations.md (## Dropping Columns)'. This is good structure with minor gaps: some deep inline detail (DropForeignKey/DropColumnConstraints semantics, the cross-language NOT NULL section) is arguably reference material embedded in the overview, which is the score-4 anchor rather than the cleanly split score-5 anchor.

Specificity

The description enumerates multiple concrete capability areas — 'creating, adjusting, or reviewing Django/Postgres migrations, including non-blocking index/constraint changes, multi-phase schema changes, data backfills, migration conflict rebasing, and product model moves that require SeparateDatabaseAndState' — and extends coverage to deletions ('any deletion or removal of a model, table, column, product, or app'). This matches the 'multiple specific concrete actions; comprehensive coverage' anchor rather than the score-4 anchor, which expects minor gaps in coverage; none are evident within the stated domain.

Completeness

It explicitly answers both questions: 'what' ('Django migration patterns and safety workflow for PostHog') and 'when' via two concrete 'Use when'/'Also use for' clauses with specific trigger conditions ('even when no migration is written'). This matches the score-5 example's structure exactly; the score-4 anchor's 'when could be more explicit' does not apply.

Trigger Term Quality

Natural phrases a user would say are well covered: 'Django/Postgres migrations', 'data backfills', 'migration conflict rebasing', 'deleting migration files', 'retiring a feature', 'non-blocking index/constraint changes'. It falls short of the score-5 anchor ('comprehensive coverage of natural terms including synonyms and file extensions') because a few plausible variants are absent — e.g., 'PostgreSQL', 'squash/squashing migrations', 'zero-downtime' — though it clearly exceeds 'a few natural terms missing' being the only gap.

Distinctiveness Conflict Risk

The niche is sharply defined — Django/Postgres migrations specifically for PostHog, with named machinery like SeparateDatabaseAndState — so it is clearly distinguishable from generic Django or database skills. The body even disambiguates the nearest neighbor ('If the task is a ClickHouse migration, use clickhouse-migrations instead'), matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.