implementlisted

Task: $ARGUMENTS If it is a path to a file, read the file first. 1. Read the task and its criteria, and the files it touches. If it is a plan, use the executing-plans skill instead of the steps below. 2. Show a short plan, 7 lines at most: files to change, and how each criterion will be checked. If the work turns out not to be bounded, stop and use brainstorming. 3. Implement with the test-driven-development skill. Keep the diff minimal and do no side refactoring. 4. Run the kit verify script (or the commands in CLAUDE.md). If something fails, fix the cause and run it again. 5. Finish with the verification-before-completion report: changed files, commands run with results, each criterion and how it was verified, and what remains unverified. Report only checks that actually ran in this session.