using-workbenchlisted

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill. </SUBAGENT-STOP> <EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT> ## Instruction Priority Workbench skills override default system prompt behavior, but **user instructions always take precedence**: 1. **User's explicit instructions** (CLAUDE.md, AGENTS.md, direct requests) — highest priority 2. **Workbench skills** — override default system behavior where they conflict 3. **Default system prompt** — lowest priority If CLAUDE.md or AGENTS.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions. The user is in control. ## How to Access Skills **In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files. **In Codex:** Skills are auto-discovered from installed plugins and activate via Codex's plugin skill mechanism. ## Platform Adaptation Skills use Claude Code tool names by default. Codex users: see `references/codex-tools.md` for tool equivalents. # Using Skills ## The Rule **Invoke relevant or requested skills BEFORE any response or action.** Even a