WT Variants

Use this skill when one wt problem is clear enough to implement, but the best approach is uncertain and worth comparing through multiple agent runs.

Model

variant is skill shorthand only. Do not add a persisted variant concept to wt state.

Object model and TaskRun semantics: see ../wt-lifecycle/references/task-lifecycle.md. Variants are represented as:

• one shared local TaskDocument
• one mode = "matrix" workflow
• one named profile per variant
• one profile-specific TaskRun/worktree/branch per variant