5K

Subject Hygiene for Task Delegation

Requires a specific action-plus-target subject on every subagent task so each delegated job stays traceable and easy to reference

emerging Updated 2026-10-13 By Nikola Balic (@nibzard) Based on Analysis of 88 Claude conversation sessions (author's own analysis, now offline), Anthropic Claude Code subagent guidance
View .md Edit on GitHub
Add to Pack
or

Saved locally in this browser for now.

Cite This Pattern
APA 
Nikola Balic (@nibzard) (2026). Subject Hygiene for Task Delegation. In *Awesome Agentic Patterns*. Retrieved October 14, 2026, from https://agentic-patterns.com/patterns/subject-hygiene
BibTeX 
@misc{agentic_patterns_subject-hygiene,
  title = {Subject Hygiene for Task Delegation},
  author = {Nikola Balic (@nibzard)},
  year = {2026},
  howpublished = {\url{https://agentic-patterns.com/patterns/subject-hygiene}},
  note = {Awesome Agentic Patterns}
}

Use when

  • Main agent delegates work to subagents via a Task tool
  • Several subagents run in parallel
  • Users or the main agent must review subagent output later

Avoid when

  • No subagent delegation in the workflow
  • Single short delegation that nobody will reference again

Problem

When delegating work to subagents via the Task tool, empty or generic task subjects make conversations:

  • Untraceable: Cannot identify what a subagent was working on
  • Unreferencable: Cannot discuss specific subagent work later
  • Confusing: Multiple subagents with empty subjects are indistinguishable

From 48 Task invocations across 88 sessions, empty task subjects were identified as a major pain point (the author's own session analysis; the repository that hosted it is no longer online, so treat the counts as anecdotal). This pattern has strong academic foundations in multi-agent communication standards (FIPA ACL, KQML) and distributed systems naming principles (REST, MapReduce).

Solution

Enforce clear, specific task subjects for every Task tool invocation. This is a meta-pattern that enables the effectiveness of all sub-agent delegation patterns (parallel spawning, factory over assistant, planner-worker). A good subject should:

  1. Not be empty (baseline requirement)
  2. Be specific and descriptive (what is being done)
  3. Be reference-able (can be discussed later)
  4. Follow naming conventions (imperative mood, clear target)

Examples:

❌ Bad subjects:

  • "" (empty)
  • "research"
  • "explore"
  • "task"

✅ Good subjects:

  • "Explore newsletter component implementation"
  • "Search for dark mode patterns in codebase"
  • "Analyze error handling in API routes"
  • "Find all OAuth configuration files"
flowchart LR A[Need to delegate] --> B{Subject clear?} B -->|No| C[Define specific subject] C --> D[Action verb + target] D --> E[Reference-able description] E --> F[Invoke Task tool] B -->|Yes| F F --> G[Subagent with clear identity] G --> H[Traceable conversation] H --> I[Discussable results] style C fill:#ffebee style D fill:#e8f5e9 style E fill:#e8f5e9 style G fill:#e8f5e9

How to use it

Before invoking Task tool, verify the subject meets all criteria:

  1. Length check: Minimum 3-4 words
  2. Action check: Starts with verb (Explore, Analyze, Search, Find)
  3. Target check: Specifies what is being acted upon
  4. Reference check: Could you point to this conversation later and say "the one that [subject]"?

Template for good subjects:

[Action Verb] + [Target/Scope] + [Optional Context]

Examples:

  • "Explore + newsletter component + implementation details"
  • "Search + codebase + for dark mode patterns"
  • "Analyze + API routes + error handling approach"
  • "Find + all OAuth + configuration files"

Anti-pattern prevention:

Prevents "Empty Subject Anti-Pattern" which makes conversations untraceable and subagent work indistinguishable.

Observed example:

From the author's nibzard-web session with 4 parallel subagents (self-reported; underlying data no longer published):

  • agent-a7911db: "Newsletter component exploration"
  • agent-adeac17: "Modal pattern discovery"
  • agent-a03b9c9: "Search implementation research"
  • agent-b84c3d1: "Log page analysis"

Clear subjects let the main agent synthesize findings from each subagent. The general practice matches Anthropic's subagent guidance, which tells agents to write specific, task-scoped descriptions when delegating. No independent cross-tool validation exists: treat this as practical guidance, not a measured result.

Trade-offs

Pros:

  • Traceable subagent conversations
  • Reference-able work items
  • Clearer synthesis of parallel work
  • Better communication with user
  • Easier debugging of delegation issues

Cons:

  • Requires upfront thinking about subject
  • Longer subject strings (minor overhead)
  • No technical enforcement (requires discipline)

When it matters most:

  • Parallel subagent delegations (2+ agents)
  • Complex research tasks
  • Long-running subagent work
  • When user needs to review subagent output

References

  • Claude Code sub-agents documentation — official guidance on creating subagents and writing task-specific descriptions (live replacement for the original analysis)
  • Original evidence base: the author's 88-session Claude analysis (github.com/nibzard/SKILLS-AGENTIC-LESSONS) is no longer available (HTTP 404), so the session counts above cannot be independently verified
  • FIPA. "FIPA ACL Communicative Act Library Specification." 2002 - Agent communication language with conversation-id for task traceability
  • Smith, R. G. "The contract net protocol." IEEE Transactions on Computers 1980 - Task identification in distributed delegation
  • Related patterns: Sub-Agent Spawning, Parallel Tool Call Learning