一键导入
using-taskplex
Context-preservation dispatcher — routes ALL work to subagents, keeping main context thin for conversation and coordination.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Context-preservation dispatcher — routes ALL work to subagents, keeping main context thin for conversation and coordination.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Applies TDD methodology to skill authoring — test before deploy. Use when creating new skills, editing existing skills, writing SKILL.md files, or verifying skills before deployment. Also use when authoring plugin skills, improving descriptions, structuring directories, or when the user says 'make a skill' or 'turn this into a skill'. If you're about to modify a SKILL.md without testing, this skill applies.
Guides branch integration with structured options: merge, PR, keep, or discard. Use when implementation is complete and tests pass, when a worktree task is done and needs cleanup, when the user says they're finished with a branch, or when it's time to merge, create a PR, or discard experimental work.
Creates isolated git worktrees for parallel development without branch switching. Use when starting feature work that needs isolation, before executing implementation plans in parallel, or when the user asks to work on a feature without affecting current changes. Also use when brainstorm produces a design ready for implementation, or when switching branches would disrupt in-progress work.
| name | using-taskplex |
| description | Context-preservation dispatcher — routes ALL work to subagents, keeping main context thin for conversation and coordination. |
| disable-model-invocation | false |
| user-invocable | false |
You have TaskPlex — a context-preservation layer that keeps your main context window thin.
NEVER do implementation, debugging, testing, or exploration work in the main context. Always delegate to the appropriate agent. The main context is for:
| Work type | Agent | Why not main context |
|---|---|---|
| Any code change (feature, bugfix, refactor) | @taskplex-implementer | Implementation fills context with file reads, edits, test runs |
| Any bug, failure, unexpected behavior | @taskplex-debugger | Investigation traces through files, logs, hypotheses |
| Design exploration, brainstorming | @taskplex-researcher | Codebase exploration reads many files |
| Verify work is done (tests, builds) | @taskplex-verifier | Runs in background, returns evidence |
| E2E testing | @taskplex-e2e | Research + test execution = massive context |
taskplex:using-git-worktrees, taskplex:finishing-a-development-branch, taskplex:writing-skills/batch, /simplify, /debug, /loop, /plan — explain what it does for this task, give the command, STOP.