verification

name	verification
description	Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
summary	Verify full user story: browser + server + data flow + env
metadata	{"priority":7,"docs":["https://vercel.com/docs/projects/project-configuration"],"sitemap":"https://vercel.com/sitemap/docs.xml","pathPatterns":[],"bashPatterns":["\\bnext\\s+dev\\b","\\bnpm\\s+run\\s+dev\\b","\\bpnpm\\s+dev\\b","\\bbun\\s+run\\s+dev\\b","\\byarn\\s+dev\\b","\\bvite\\s*(dev)?\\b","\\bvercel\\s+dev\\b","\\bastro\\s+dev\\b"],"importPatterns":[],"promptSignals":{"phrases":["verify the flow","verify everything works","test the whole thing","does it actually work","check end to end","end to end test","why isn't it working right","why doesn't it work","it's not working correctly","something's off","not quite right","almost works but","works locally but","verify the feature","make sure it works","full verification"],"allOf":["[Truncated]","[Truncated]","[Truncated]","[Truncated]","[Truncated]","[Truncated]","[Truncated]","[Truncated]"],"anyOf":["verify","verification","end-to-end","full flow","works","working"],"noneOf":["unit test","jest","vitest","playwright test","cypress test"],"minScore":6}}
retrieval	{"aliases":["end to end test","full stack verify","flow test","integration check"],"intents":["verify full flow","test end to end","check if app works","validate implementation"],"entities":["browser","API","data flow","end-to-end","verification"]}
chainTo	[{"pattern":"process\\.env\\.\\w+|NEXT_PUBLIC_\\w+","targetSkill":"env-vars","message":"Environment variable references detected during verification — loading Env Vars guidance for proper configuration, vercel env pull, and branch scoping.","skipIfFileContains":"vercel\\s+env\\s+pull|\\.env\\.local"},{"pattern":"middleware\\.(ts|js)|proxy\\.(ts|js)|clerkMiddleware|NextResponse\\.redirect","targetSkill":"routing-middleware","message":"Middleware/proxy detected during verification — loading Routing Middleware guidance for request interception, auth checks, and proxy.ts migration."},{"pattern":"streamText\\s*\\(|generateText\\s*\\(|useChat\\s*\\(","targetSkill":"ai-sdk","message":"AI SDK calls detected during verification — loading AI SDK v6 guidance for streaming, transport, and error handling patterns.","skipIfFileContains":"toUIMessageStreamResponse|DefaultChatTransport"}]

Full-Story Verification

You are a verification orchestrator. Your job is not to run a single check — it is to infer the complete user story being built and verify every boundary in the flow with evidence.

This skill coordinates with agent-browser-verify (browser-side visual checks), investigation-mode (reactive debugging), and observability (logging/monitoring) — but your focus is the end-to-end story, not any single layer.

When This Triggers

• A dev server just started and the user wants to know if things work
• The user says something "isn't quite right" or "almost works"
• The user asks you to verify a feature or check the full flow

Step 1 — Infer the User Story

Before checking anything, determine what is being built:

1. Read recently edited files (check git diff or recent Write/Edit tool calls)
2. Identify the feature boundary: which routes, components, API endpoints, and data sources are involved
3. Scan package.json scripts, route structure (app/ or pages/), and environment files (.env*)
4. State the story in one sentence: "The user is building [X] which flows from [UI entry point] → [API route] → [data source] → [response rendering]"

Do not skip this step. Every subsequent check must be anchored to the inferred story.

Step 2 — Establish Evidence Baseline

Gather the current state across all layers:

Layer	How to check	What to capture
Browser	Use agent-browser — open the relevant page, screenshot, check console	Visual state, console errors, network failures
Server terminal	Read the terminal output from the dev server process	Startup errors, request logs, compilation warnings
Runtime logs	Run vercel logs (if deployed) or check server stdout	API response codes, error traces, timing
Environment	Check .env.local, vercel env ls, compare expected vs actual	Missing vars, wrong values, production vs development mismatch