create-walkthrough

Generate honest, argumentative walkthrough documents for complex implementations. Not a status report or handoff document. A prosecution brief where the agent argues why an implementation should succeed, admits what could go wrong, and the user pokes holes.

This is a COLLABORATIVE skill. The agent does NOT write a walkthrough alone.

Why This Exists

A walkthrough caught two real bugs before a pipeline launch:

1. A false claim about a missing dependency (agent wrote it, agent believed it, user caught it)
2. A missing semantic quality check the deterministic assessment couldn't provide