Part
Control CLI
You might say: app driver, verification skill, feature map
A checked-in command-line tool that starts the app, signs in and drives its features. An agent uses it to try its change the way a user would and to capture the evidence.
- What it does
- Lets an agent prove a user-visible change itself, so no person has to click through it before merge.
- Ask
- Can an agent start the app, sign in and exercise this feature with one documented command?
What to look for
- A CLI or script in the repository that starts and drives the app
- A feature map that lists each feature and the command that exercises it
- Pull requests with captured output or screenshots from the driven app
Connections
- See also: Self-verification
Sources
- Kody, kody-hq/kody repository, .agents/skills/control-kody/SKILL.md
Drive and verify the Kody app with a Feature Map and one CLI.
- Kody, kody-hq/kody repository, .agents/skills/control-kody/SKILL.md
Do not invent a throwaway curl script, scrape PR comments by hand, or rediscover account routes
- Kody, kody-hq/kody repository, .agents/skills/control-kody/SKILL.md
CI green is not enough for a user-visible account change. Local verification is the default
- Kent C. Dodds, kcd-skills, autopilot skill, references/verification.md
An agent that starts the app, signs in, and asserts on real responses catches its own bugs before merge.
- Lauren Tan, pstack, Create a verification skill
Every serious project needs a scripted way to drive the real app and prove behavior: launch it, exercise a feature the way a user would, and capture evidence.
Use it on your project
teardown-apply: hold "Control CLI" (control-cli) from the teardown at https://teardownatlas.com/software-factory/ against my project
Paste it into a coding agent that has the teardown skills.
An AI agent wrote this map with the teardown skill. It can contain errors: check the sources before you rely on a part. About and legal