maestro-task

# Maestro Task Use this for task work. A task is the proof-gated unit of implementation; a feature is the product contract it may deliver against. Activate: `maestro hook record --event skill_activation --skill maestro-task` ## Use - Create or prepare work: `create`, `explore`, `accept`. - Pick up work: `claim --next` or `claim <id>`. - Record progress: `update --summary` and/or `--claim`. - Finish work: `complete --summary --claim --proof`, then verify. - Handle pauses or terminal outcomes: `block`, `unblock`, `reject`, `abandon`, `supersede`. - Act on harness improvement proposals surfaced by `status`, `task next`, or `harness list`. - When the user corrects your behavior, record it with `maestro event intervention --note "<what was wrong>" [--topic <slug>]`. ## Do ```sh maestro task create "<title>" [--feature F --lane L --risk R --check "<observable result>"] maestro task explore <id> maestro task accept <id> # locks acceptance, except tiny lane may skip maestro task claim --next # prints feature and dependency context maestro task update <id> --summary "<note>" --claim "<evidence claim>" maestro task complete <id> --summary "<what changed>" --claim "<claim>" --proof "<observed evidence>" maestro task verify <id> ``` `verify` and `show` can omit `<id>` when `MAESTRO_CURRENT_TASK` is set. ## Evidence Gate `complete --proof` records proof text and auto-runs verification. Verification passes only when: - task state is `needs_ver...