wipnoteexecutelisted

# wipnote Parallel Execute Use this skill to execute development tasks in parallel using dependency-driven dispatch and worktree isolation. **Trigger keywords:** execute plan, run plan, run tasks, parallelize work, work in parallel, start execution, dispatch agents --- ## Environment When running in a worktree, `WIPNOTE_PROJECT_DIR` is set automatically. All `wipnote` CLI commands resolve to the main project's `.wipnote/` — no need to `cd` to main. Just run commands directly: `wipnote track show <id>`. **NEVER use bare `cd` in Bash** — the hook will block it. Use subshells if you must change directories: `(cd dir && command)`. --- ## Efficiency Rules (read before dispatching) Every tool call spends a turn. The goal is to dispatch the first subagent within **≤5 tool calls**. To hit that budget: 1. **One call, not ten.** Use `wipnote execute-preview <trk-id> --format json` to get the track, linked features/bugs/plans, and current git state in a single invocation. Do not call `wipnote track show`, `wipnote feature show`, `wipnote plan show`, and `git status` separately before the first dispatch. 2. **Batch git-state probes.** If execute-preview doesn't cover a probe you need, chain with `&&` in one Bash call — never one tool call per git subcommand. 3. **Don't feature-show more than twice in a row.** If you find yourself calling `wipnote feature show` for every linked feature, stop and re-read the preview JSON — the status you need is already there. 4. **Don't retry fl