Conciseness

The body is lean with no padding about what a game, POI, or simulation is; every line carries actionable instruction and assumes Claude's competence, matching the 'lean and efficient, every token earns its place' anchor.

Actionability

Provides copy-paste-ready commands (pytest tests/test_death.py, npm run type-check, npm run test -- src/__tests__/composables/useTextures.test.ts) plus concrete API fields to check (is_dead, death_info, pois kind: "grave", deceased_avatar_id) and a specific approach (high-age avatar), covering the common cases fully executably.

Workflow Clarity

A clear 5-step sequence includes explicit validation (step 4 API causal-chain checks, the 最小验证 test block) and a cleanup checklist with pre-deletion核对, satisfying the destructive-skill validation requirement and the 'explicit validation steps with feedback loops' anchor.

Progressive Disclosure

Under 50 lines and single-purpose with well-organized sections (流程, 最小验证, 清理); the sole external reference (docs/specs/external-control-api.md) is one level deep and clearly signaled inline, and no bundle files exist to require further splitting.

Specificity

Names the domain (in-game death testing) and several concrete verification actions — 角色死亡, 墓碑 POI 创建, 地图渲染, 点击详情 — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive anchor 5.

Completeness

Explicitly answers 'what' (验证角色死亡、墓碑 POI 创建、地图渲染和点击详情) and 'when' (用于需要测试…的任务) with concrete trigger phrases, matching the anchor for clearly answering both what and when.

Trigger Term Quality

Includes natural phrases a user would say — 寿元死亡, 游戏内死亡流程, 墓碑 POI — giving good keyword coverage, though a few synonyms or variants are absent so it stops short of the comprehensive anchor 5.

Distinctiveness Conflict Risk

Occupies a clear niche (death/grave-POI verification via real simulation) reinforced by the distinctive constraint 不得直接调用 handle_death, yielding distinct triggers and minimal conflict risk.