shipping-tasklisted

## Select the mode Resolve an unknown target through [work-on](../work-on/SKILL.md). Read `forbidDirectCommit` and `gitWorkflowSkill` from the [apps configuration](../init/references/apps-config-schema.md). Reuse the user's established mode and base branch. Otherwise ask how the user regards this piece of work, with these consequences: - **solo-mode:** work in the primary checkout and commit directly to the base branch. - **team-mode:** worktree → develop → MR/PR → merge → archive. `forbidDirectCommit: true` selects team-mode automatically. For a batch, ask once for the remaining items' shared default. Before solo work starts, check the primary checkout is clean and reserve it for one task at a time; resolve existing changes with their owner. ## Prepare and execute The execution tier comes from [boss-say](../boss-say/SKILL.md#route-the-work). In team-mode, the main agent creates and verifies the worktree and copies declared local files through [Worktree ownership](../dispatching-work/references/plan-mechanics.md#worktree-ownership). The verified path becomes the worker's cwd. The execution owner loads the target's instructions and uses its source-change workflow. For post-worktree git operations, run `gitWorkflowSkill` when configured; otherwise commit the change, and in team-mode push the feature branch and open an MR/PR. Separate workrooms use [dispatching-work](../dispatching-work/SKILL.md), including its brief contract. ## Mutation checkpoints Apply existing user