harden-task-file

**User request**: $ARGUMENTS Systematically harden a /define task guidance file until manifests built from it produce deliverables that don't need iteration. If no arguments, ask which task file to harden. ## Context Task files come in two parallel, decoupled sets, each keyed by task type and hardened for one-shot quality. Harden whichever set the target file belongs to: - **`/define`'s task files** (`claude-plugins/manifest-dev/skills/define/tasks/`) carry encoder data: - **Quality Gates** — Verifiable output properties. Can split into baselines (always enforced) and selectable (meaningful rigor choices) - **Defaults** — Non-verifiable process practices always worth doing, encoded as PG-* without probing - **figure-out's task files** (`claude-plugins/manifest-dev/skills/figure-out/tasks/`) carry probing fuel: - **Blind-spot probes** — Non-natural angles the model skips by default (failure modes, pre-mortem fuel), phrased as the question that opens a branch - **Forced trade-offs** — Competing tensions the model must drive to a decision New items must match the depth and structural conventions of the owning skill (`define/SKILL.md` or `figure-out/SKILL.md`) and its existing sibling task files. ## Goal The task file should be comprehensive enough that a manifest built with it surfaces all criteria needed for one-shot quality — figure-out's probes surface the non-natural angles during understanding; /define's gates and Defaults encode the verifiable bar. "One-sho...