The Complete Guide to pstack, Pt. 1: Verification Is All You Need
poteto argues that a verification skill — an agent's ability to drive the app, screenshot it, read traces and confirm its own change — is critical infrastructure rather than a nice-to-have, because it takes the human out of the loop. The post walks through /create-verification-skill: wrap dev-environment control in an agent-friendly CLI (doctor, snapshot, screenshot, wait-settle, feature-flag), then catalog every feature in a markdown Feature Map describing what it does, how a user reaches it, and known gotchas. She advises against scaling with git worktrees (roughly 10 agents per machine before resources bite) and recommends Cursor cloud agents plus /swarm for parallel verification runs. Wired into a scheduled routine, the skill can auto-reproduce user bug reports from Slack. The CLI design rules — --dry-run on destructive commands, descriptive errors, JSON output, progressive disclosure via subcommands — are the most transferable part. Claims of 2,000 PRs/month and 100-1000x output come with no measurement.