dev-verifylisted

# Verify Verify phase: define → build → **verify** **Trigger**: `/dev-verify {feature-name}` or `/dev-verify {feature-name} {feedback}` ## Input Formats ``` /dev-verify user-registration # hybrid: auto + manual /dev-verify user-registration 1:PASS 2:FAIL no validation # inline feedback (skips automation) /dev-verify user-registration Everything works except... # free text (skips automation) ``` > Classification criteria: `references/test-classification.md` > Code quality rules: `../shared/CODING-RULES.md` (R007-R009, T001-T203, TST001-TST203). Frontend projects: also `../shared/FRONTEND-RULES.md`. ## Workflow **Phase tracking** — first action of the skill: call `TaskCreate` with the 5 mandatory phases (status `pending`): 1. PHASE 0: Load Context and Classify 2. PHASE 1: Automated Testing (skip if no AUTO items — mark completed without work) 3. PHASE 2b: Combined Results 4. PHASE 5d: Requirement Verification 5. PHASE 6: Completion **Worktree check** — after resolving `feature-name` in PHASE 0 Step 1, detect whether a worktree exists for this feature: ```bash git worktree list --porcelain | grep -q "branch refs/heads/worktree-{feature-name}$" ``` Match → add PHASE Finalize at end via `TaskCreate`. (PHASE Finalize itself decides whether to act based on test outcome — always add it when a worktree exists, regardless of which checkout currently runs the skill.) Add fix-loop phases via `TaskCreate` ONLY when they will fire: - Inline fee