القائمة
Launch one or more tasks in new git worktrees using workmux.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | worktree |
| description | Launch one or more tasks in new git worktrees using workmux. |
| disable-model-invocation | true |
| allowed-tools | Bash, Write |
Launch one or more tasks in new git worktrees using workmux.
Tasks: $ARGUMENTS
HARD RULE — NO EXCEPTIONS: Do NOT explore, read, grep, glob, or search the
codebase. Do NOT use the Task/Explore agent. Do NOT investigate the problem. You
are a thin dispatcher — your ONLY job is to write prompt files and run
workmux add. The worktree agent will do all the exploration and implementation.
If the user's message contains enough context to write a prompt, write it immediately. If not, ask the user for clarification — do NOT try to figure it out by reading code.
If tasks reference earlier conversation (e.g., "do option 2"), include all relevant context in each prompt you write.
If tasks reference a markdown file (e.g., a plan or spec), re-read the file to ensure you have the latest version before writing prompts.
For each task:
workmux add <worktree-name> -b -P <temp-file> to create the worktreeThe prompt file should:
If the user passes a skill reference (e.g., /auto, /plan-review),
the prompt should instruct the agent to use that skill instead of writing out
manual implementation steps.
Skills can have flags. If the user passes /auto --gemini, pass the
flag through to the skill invocation in the prompt.
Example prompt:
[Task description here]
Use the skill: /skill-name [flags if any] [task description]
Do NOT write detailed implementation steps when a skill is specified — the skill handles that.
--merge: When passed, add instruction to use /merge skill at the end to
commit, rebase, and merge the branch.
...
Then use the /merge skill to commit, rebase, and merge the branch.
Only instruct worktree agent to /merge if explicitly requested by user in
task.
--fork: When passed, add --fork to the workmux add command. This copies
the current conversation into the new worktree so the agent resumes with full
context of what was discussed. Useful when the current conversation has built up
context that the new worktree agent needs.
Write ALL temp files first, THEN run all workmux commands.
IMPORTANT: Run workmux add from the CURRENT directory. Do NOT cd to the
main repo or any other directory. The new worktree branches from whatever branch
is checked out in the current directory.
Step 1 - Write all prompt files (in parallel):
tmpfile=$(mktemp).md
cat > "$tmpfile" << 'EOF'
Implement feature X...
EOF
echo "$tmpfile" # Note the path for step 2
Step 2 - After ALL files are written, run workmux commands (in parallel):
workmux add feature-x -b -P /tmp/tmp.abc123.md
workmux add feature-y -b -P /tmp/tmp.def456.md
After creating the worktrees, inform the user which branches were created.
Remember: Your task is COMPLETE once worktrees are created. Do NOT implement anything yourself.
Universal commenting and documentation conventions across all languages. Load when writing or reviewing substantial comments, docstrings, file headers, or migration documentation. Project-specific commenting standards in `docs/commenting-standard.md` (when present) extend or override this baseline.
Exhaustive post-work audit for any codebase. Run after finishing a feature, sprint, bug fix, or refactoring pass to find overlooked edge cases, discarded response data, missing cross-field validations, misleading success signals, untested failure paths, and implicit assumptions. Invoke with /deep-audit or /deep-audit followed by context. Use this skill whenever the user says audit, review my changes, check my work, what did I miss, post-mortem, sanity check, edge cases, or asks to verify completeness of recent code changes.
Use when modifying the agentic coding environment, including dotfiles, skills/rules wiring, AGENTS.md/CLAUDE.md loading, Stow symlinks, Claude/Codex/OpenCode/Pi config, plugins, MCP, hooks, or harness compatibility. Loads the runbook to avoid breaking cross-harness setup. Defer to skill-creator-global for skill authoring craft, description quality, and progressive disclosure.
Retrieves up-to-date documentation, API references, and code examples for any developer technology via the ctx7 (Context7) CLI. Use this skill whenever the user mentions "ctx7" or "context7", or asks about a specific library, framework, SDK, CLI tool, or cloud service -- even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer -- do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Create, revise, or review Agent Skills for authoring quality. Use when writing SKILL.md content, improving skill descriptions and trigger words, deciding what belongs in SKILL.md versus references/scripts, or diagnosing why a skill over-triggers or under-triggers. Defer to agentic-coding-harnesses for dotfiles, Stow, symlinks, harness visibility, AGENTS.md, plugins, MCP, or environment wiring.