Demo video

One real Claude Code session, about 22 minutes, cut to 10 by speeding up the waiting. Every stage is driven by an agent skill: wfnexus-setup installs the Docker stack on free models, workflow-author builds Priya's Friday release-notes workflow, wfnexus-deploy publishes and schedules it, and approval-desk puts every change in front of her. She rejects a draft, a fix goes through review, the agent finds a real bug in the skill's own example, and v1.0.2 ships.

wfnexus · one real Claude Code session · no voice, subtitles on

• 0:05Install (wfnexus-setup)
• 1:36Build the workflow (workflow-author)
• 3:44Deploy to the team server (wfnexus-deploy)
• 5:10The approval gate (approval-desk)
• 6:32Reject, fix, re-ship
• 9:02Approved: the notes as committed

What the workflow does

1. Gather. It collects the week’s commits from git log, leaving out merges.
2. Classify. A calibrated classifier (jev-1.13) labels each commit as feature, fix, security, breaking or internal.
3. Draft. An agent on a free model writes customer-facing notes. Internal commits are left out.
4. Review. A second agent checks every claim against the actual commit. All six claims were backed.
5. Gate, then publish. Nothing is written until a human approves. Then RELEASE_NOTES.md is committed.

Run it yourself

bash skills/wfnexus-setup/scripts/setup.sh --port 8390 --project wfxdemo   # install: READY <url>
wfx install --skills                                                       # the agent skills, for Claude/Codex
bash skills/wfnexus-deploy/scripts/deploy.sh release-notes.yaml --project acme-api --version v1.0.0
wfx run release-notes -f                                                   # run it, follow the log
wfx approve <run-id>                                                       # the human gate

Or say it to Claude Code with the skills installed: “set up wfnexus”, “turn my Friday release notes into a workflow”, “deploy it”, “show me what is waiting”.

What else the session showed (unscripted)

• Claude wrote the YAML itself. The wfx CLI has no commands for building steps yet.
• It stopped at your rules. Editing .env was denied by the owner’s own rule, so it did not try another way.
• The reviewer rejected the first draft, and Claude traced it to its own prompt being stricter than the rule it was given, then fixed the prompt.
• A real bug in the product, found on camera: the workflow-author skill’s example put default’s fallback second, so an input was silently ignored. Fixed in the same change that published this video, with a test that fails if any shipped skill or template does it again.
• Claude approved one proposal on its own during the build, before being told to ask first. After that, every approval went to Priya.