Decision guide for choosing the right specialized agent for each task type
Selects the optimal specialized agent for each task by analyzing requirements, complexity, and context—not just keywords. Use when dispatching ad-hoc tasks to ensure debugging, development, or review work goes to the right agent.
/plugin marketplace add cipherstash/cipherpowers/plugin install cipherpowers@cipherpowersThis skill inherits all available tools. When active, it can use any tool Claude has access to.
test-pressure-1.mdtest-pressure-2.mdtest-pressure-3.mdUse the right agent for the job. Each agent is optimized for specific scenarios and follows a focused workflow.
This skill helps you choose which specialized agent to use based on the task at hand.
For automatic agent selection: When executing implementation plans, use the /cipherpowers:execute command which applies this skill's logic automatically with hybrid keyword/LLM analysis. Manual selection using this skill is for ad-hoc agent dispatch outside of plan execution.
When selecting agents (manually or automatically), you must analyze the task requirements and context, not just match keywords naively.
DO NOT use naive keyword matching:
DO use semantic understanding:
Examples of INCORRECT selection:
Examples of CORRECT selection:
Selection criteria:
Red flags that indicate you're selecting incorrectly:
When to use: After code changes that affect documentation
Scenarios:
Skill used: maintaining-docs-after-changes
Command: /cipherpowers:verify docs
Key characteristic: Reactive to code changes - syncs docs with current code state
When to use: Complex, multi-layered debugging requiring deep investigation
Scenarios:
Skills used: systematic-debugging, root-cause-tracing, defense-in-depth, verification-before-completion
Key characteristic: Opus-level investigation for complex scenarios, not simple bugs
When to use: Rust development tasks requiring TDD and code review discipline
Scenarios:
Skills used: test-driven-development, testing-anti-patterns, code-review-reception
Key characteristic: Enforces TDD, mandatory code review, project task usage
When to use: Reviewing code changes before merging
Scenarios:
Skill used: conducting-code-review
Command: /cipherpowers:code-review
Key characteristic: Structured review process with severity levels (BLOCKING/NON-BLOCKING)
When to use: Evaluating implementation plans before execution
Scenarios:
/cipherpowers:plan/cipherpowers:executeSkill used: verifying-plans
Command: /cipherpowers:verify plan
Key characteristic: Evaluates plan against 35 quality criteria across 6 categories (Security, Testing, Architecture, Error Handling, Code Quality, Process)
| Confusion | Correct Choice | Why |
|---|---|---|
| "Just finished feature, need docs" | technical-writer + /summarise | technical-writer syncs API/feature docs, /summarise captures learning |
| "Quick docs update" | technical-writer | All doc maintenance uses systematic process |
| "Fixed bug, should document" | /summarise command | Capturing what you learned, not updating technical docs |
| "Changed README" | Depends | Updated feature docs = technical-writer. Captured work summary = /summarise |
| "Production debugging done" | /summarise command | Document the investigation insights and lessons learned |
Scenario 1: Added new API endpoint → technical-writer - Code changed, docs need sync
Scenario 2: Spent 3 hours debugging Azure timeout → /summarise command - Capture the investigation, decisions, solution
Scenario 3: Both apply - finished user authentication feature → technical-writer first - Update API docs, configuration guide → /summarise second - Capture why you chose OAuth2, what issues you hit
Scenario 4: Random test failures in CI → ultrathink-debugger - Complex timing/environment issue needs deep investigation
Scenario 5: Simple bug fix in Rust → rust-agent - Standard development workflow with TDD
Scenario 6: Just finished writing implementation plan → plan-review-agent - Validate plan before execution
Scenario 7: About to execute plan, want quality check → plan-review-agent - Ensure plan is comprehensive and executable
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.