team-verifylisted

# Verify — Teammate Verification ## Overview Verify teammate code delivery. Detects available context (feature.json with requirements, backlog TODO with description, or just a branch diff), checks completeness where possible, generates and runs tests, and produces structured feedback. **Trigger**: `/team-verify` or `/team-verify {feature-name}` or `/team-verify {feature-name} {feedback}` ## When to Use - After teammate delivers code on a feature (with or without `/dev-define`) - When teammate pushes code for a backlog TODO item - When teammate branch code needs verification before merge **NOT for:** - Testing own code (use `/dev-verify`) - Unit-level test writing during build (use `/dev-build`) ## Input Formats ``` # Auto-detect context (recommended) /team-verify # Specific feature /team-verify user-registration # Inline feedback (skips automation) /team-verify user-registration 1:PASS 2:FAIL no validation error 3:PASS ``` ## Workflow **Phase tracking** — first action of the skill: call `TaskCreate` with these 12 items (status `pending`), then use `TaskUpdate` to set each phase `in_progress` at the start and `completed` at the end. During context compaction the task list remains visible — no risk of skipping phases. 1. PHASE 0: Context Detection 2. PHASE 0.5: Completeness Check 3. PHASE 1: Research + Scenario Generation 4. PHASE 2: Test Plan + Classification 5. PHASE 3: Automated Test Execution 6. PHASE 4: Manual Test Execution 7. PHASE 4b: Combined Results 8. P