worklisted

# Work Act as the accountable lead for a free-form task. Keep the vision, requirements, decisions, integration, and final proof in the parent thread. Use bounded agents as executors; never make them substitute bosses. Read [`skills/QUALITY.md`](skills/QUALITY.md) before acting. It is binding: quality software must not break, demand attention, exceed its limits, or preserve backwards compatibility. The parent owns the exact task statement, taste, user-facing copy, integration, proof, and escalation when an external contract cannot be removed. For test work, apply the [meaningful testing standard](skills/QUALITY.md#meaningful-testing): inspect the implementation, existing tests, public APIs, and actual user flows before writing anything; protect observed behavior with a few deterministic tests; and report justified omissions and real bugs instead of optimizing coverage. ## Dedicated Work skills Use the separate skill that matches the user's intent. Do not make the user remember subcommands: | Skill | Purpose | |---|---| | `$work-init` | Guide and verify a minimal new project setup | | `$work-ideate` | Challenge assumptions, explore distinct directions, and shape a testable idea | | `$work-plan` | Sol xhigh read-only analysis with a detailed implementation-ready plan | | `$work-test` | Inspect real behavior and add only justified deterministic tests | | `$work-concern` | Surface concrete implementation concerns without edits or a full audit | | `$work-checklist` | Turn con