diamond-assesslisted

# Diamond Assess Skill Evaluate current diamond state and recommend next action. ## Preflight: Read-before-Recommend (gate-narration discipline) **Hard rule** (per CLAUDE.md Communication Rules, anti-pattern #7 graduation v0.39.16). Every gate-status narration, blocker statement, hold claim, or "what's missing" verdict this skill emits MUST cite the canvas file + field path of the source evidence (e.g., `per purpose.yml#why`, `per opportunities.yml#opp-005#status`, `per landscape.yml:1520`). Adjacent-surface inference (different opportunity, different ht, different topic) MUST be tagged as inference, not asserted as gate state. This skill ran an un-mechanized version of its own diagnosis in cluster-instances.md instance #17 (2026-06-02) — confabulated an "L0 unclear" blocker from comms-friction evidence while the L0 purpose was clear and canvas-documented; collapsed only after the founder articulated the underlying model and grep verified the canvas already had it. The preamble exists so this skill stops being the recursive case. ## Workflow 0. **Cognitive Forcing (ALWAYS FIRST — before any analysis)**: Before presenting any assessment, ask the human for their unprimed judgment: > "Before I run the gates — where do you think this diamond stands right now? What feels solid and what feels shaky?" Wait for the human's response. Record it. Then proceed with the full assessment below. After presenting the assessment (step 10), compare: > "You said [X]. The gat