before-spawning-task

Select specialized subagent_type mappings for codebase, documentation, and web research tasks.

10|2|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/eveld/claude --skill before-spawning-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: before-spawning-task
Source: https://github.com/eveld/claude/tree/main/skills/before-spawning-task
Command: npx skills add https://github.com/eveld/claude --skill before-spawning-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Avoids accidentally using generic agents by enforcing the use of specialized subagent_type mappings for common tasks, reducing misrouting and inefficiency.

Core Features & Use Cases

  • Enforces explicit mappings from task types to specialized subagents (e.g., codebase-locator for finding files, codebase-analyzer for understanding code, codebase-pattern-finder for pattern discovery, thoughts-locator for documentation, thoughts-analyzer for document analysis, web-search-researcher for web research).
  • Provides safe fallbacks only when no specialized match exists, with clear prompts to switch.
  • Improves task accuracy and compliance with safety guardrails by guiding agent selection.

Quick Start

Instruct Claude to use the specialized subagent_type mappings before executing any task.

Frequently Asked Questions about before-spawning-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route tasks to specialized agents instead of generic ones?

To route tasks to specialized agents, you enforce explicit mappings from task types to specific subagent_type values, such as codebase-locator for finding files, which eliminates accidental generic agent usage.

What is the best way to ensure task routing uses specialized subagent types?

The best way to ensure task routing uses specialized subagent types is to apply explicit task-type mappings and include a guardrail that falls back to generic agents only when no specialization matches.

How do I map codebase exploration tasks to the correct subagent type?

You map codebase exploration tasks by assigning specific subagent types: codebase-locator to find files, codebase-analyzer to understand code, and codebase-pattern-finder to discover patterns.

When should I use a generic agent fallback during task routing?

You should use a generic agent fallback during task routing only when no specialized subagent_type matches your specific task, ensuring safe execution without misrouting.

Does this workflow support web research and documentation analysis?

This workflow supports web research and documentation analysis by routing those tasks to specialized agents like web-search-researcher, thoughts-locator, and thoughts-analyzer.

Why does my workflow accidentally use generic agents for specialized tasks?

Your workflow accidentally uses generic agents because it lacks enforced specialized subagent_type mappings, allowing tasks to misroute without explicit guardrails or fallback constraints.