harnessloop-goallisted

# Harnessloop Goal Manage Harnessloop goals as contracts. This skill edits or reports goal structure, subgoals, tasks, thresholds, and goal lifecycle state; execution remains with `$harnessloop-continue` or `$harnessloop-loop`. ## Input Contract Accept explicit skill invocations such as `$harnessloop-goal status`, `$harnessloop-goal propose`, `$harnessloop-goal negotiate`, `$harnessloop-goal update`, `$harnessloop-goal split`, `$harnessloop-goal reprioritize`, `$harnessloop-goal archive`, `$harnessloop-goal cancel`, `$harnessloop-goal supersede`, or `$harnessloop-goal deletion-impact`. Treat `harnessloop:goal` as a natural-language alias only; `$harnessloop:goal` is not a valid skill invocation. Useful input includes: - `target-project`: defaults to the current working directory. - `action`: `status`, `propose`, `negotiate`, `update`, `split`, `reprioritize`, `archive`, `cancel`, `supersede`, or `deletion-impact`. - `goal-path`: existing `.harnessloop/goals/YYYYMMDD-NNN-<goal-slug>/` when applicable. - `goal-contract`: goal, non-goals, success condition, acceptance criteria, required human decisions, and ambiguity. - `subgoals-or-tasks`: proposed or existing subgoal/task list with dependencies, priority, risk, expected evidence, and validation method. - `change-reason`: why the goal contract or breakdown is changing. - `human-confirmation`: required for material goal contract changes, cancellation, supersession, deletion impact, or current-round impact. If `.harnessloop