# Verify Understanding > Verify the engineer is ready to implement a feature — a teach-back conversation over a .TICKET-REVIEW.md where they explain the feature in their own words and the agent probes and corrects. - Skill: `eai-org/verify-understanding` (Agent Skill) - Install (CLI): `npx skillmds@latest add eai-org/verify-understanding` - Raw SKILL.md: https://api.skillmd.com/api/skills/eai-org/verify-understanding/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - License: MIT - Author: eai-org (https://skillmd.com/u/eai-org) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/eai-org/verify-understanding --- # Verify understanding One goal, nothing more, nothing less: verify the engineer is ready to move to the implementation phase. Exercise their understanding of a feature before they work on it — the pipeline's other artifacts serve fresh agent sessions; this step serves the human. Active recall: the user produces the feature in their own words, you only steer and fix. Re-runnable: right after the ticket review, or days later just before implementation — every run starts fresh from the review file, no state kept between runs. ## Input A `.TICKET-REVIEW.md`. Read it and the ticket files and parent it links. A reference that exists only as a tracker URL (no local file) may be fetched read-only at conversation time. ## The conversation A conversation, not a test — the last sync between a dev and their PO before development starts. 1. Ask the user to explain the feature in their own words: who uses it, what they see and do, why the feature exists, and what each ticket contributes. 2. Let them produce the narrative. Probe one weak spot at a time; correct and complete only from the review file and the referenced materials — flag what those don't settle, never improvise requirements. 3. Stay at that PO–dev depth: journey, actors, purpose, per-ticket contribution — not DTO, field, or architecture detail. When the product's user-facing language differs from the conversation's, name each page, text, or element with its user-facing term in parentheses — "the client area (klantportaal)". Done when the user has correctly produced — corrections absorbed — the journey, why the feature exists, and every input ticket's contribution: enough to start implementing. Close with a short wrap-up naming anything that stayed shaky, then point at `/refine-ticket ` per ticket, in the set's suggested execution order. ## Boundaries - The conversation is the product: write no files. - Read-only on the tracker.