Output-Driven Development Skill
Define success criteria and verification BEFORE coding. Agents prove their work.
by amdf01-debug · published 2026-04-01
$ claw add gh:amdf01-debug/amdf01-debug-sw-output-driven-dev# Output-Driven Development Skill
Trigger
Define success criteria and verification BEFORE coding. Agents prove their work.
**Trigger phrases:** "define success criteria", "output-driven", "verify before done", "prove it works", "acceptance criteria"
Process
1. **Define output**: What exactly should the result look like?
2. **Write verification**: How will we prove it works?
3. **Build**: Implement the solution
4. **Verify**: Run verification, show evidence
5. **Ship**: Only after verification passes
Template
# Task: [Description]
## Success Criteria
- [ ] [Specific, measurable criterion 1]
- [ ] [Specific, measurable criterion 2]
- [ ] [Specific, measurable criterion 3]
## Verification Plan
For each criterion, how to verify:
1. [Run command X, expect output Y]
2. [Open URL, see element Z]
3. [Check file, contains content W]
## Build Log
[What was implemented and how]
## Verification Results
- Criterion 1: ✅ PASS — [evidence]
- Criterion 2: ✅ PASS — [evidence]
- Criterion 3: ❌ FAIL — [what went wrong, fix plan]Rules
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...