demolisted

Demonstrate landed work instead of just claiming it shipped. Recover the ORIGINAL intent (not the diff), exercise the shipped thing in its REAL environment — the installed/deployed artifact, never the dev build — drive it on the real surface with `agents browser`/`agents computer` signed in as the owner on REAL representative inputs (never toy examples), put before/after side by side with a measured delta, then deliver an analyzed HTML report on the owner's screen and attach it to the PR. Triggers on: /demo, /work:demo, 'show me a demo', 'prove it works', 'test it in prod', 'how does it look side by side', 'did we ship all of it', 'demo what we just shipped', after any landing/merge/release.
phnx-labs/.agents · ★ 0 · Code & Development · score 62

Install: claude install-skill phnx-labs/.agents

# work:demo — prove it, don't just ship it An agent that lands a feature and stops at *"it's merged / shipped / released"* has done **half** the job. The code compiling and the PR merging is not a demonstration that the thing the owner **asked for** actually works. `/demo` is the missing capstone: you take the original intent, run the shipped thing against **real** inputs in its **real** environment, put before and after side by side, and hand the owner a report — so they never have to type *"show me a demo.."* themselves. **The bar is the INTENT, not the diff.** "I wrote the code and it merged" is the thing you are testing, not the proof. You are proving the owner got what they asked for. ## When this runs - Right after you (or a teammate) land something user-visible — a feature, a fix, a release. Reach for it yourself the moment work lands; don't wait to be asked. - When the owner says *"show me a demo"*, *"how does it look side by side"*, *"did we ship all of it"*, *"test it in prod"*. ## The argument - **No argument** → demo what **THIS session** just landed. Recover the intent from the transcript (the opening ask), the ticket you worked, and the PR you merged. - **An argument** (`PHNX-1234`, a PR URL, a session id, or a description) → demo that landing. Pull its intent from the ticket + PR + any prior session on the topic. --- ## Step 1 — Recover the intent (don't trust the diff) Before touching the product, reconstruct **what was actually asked for**: