spawn-decision

Spawn a decision-agent to determine when orchestration is needed for complex judgments.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/Zeliper/z-coder --skill spawn-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawn-decision
Source: https://github.com/Zeliper/z-coder/tree/main/.claude/skills/spawn-decision
Command: npx skills add https://github.com/Zeliper/z-coder --skill spawn-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides when and how to use the decision-agent to handle complex judgments, reducing manual orchestration and unnecessary /orchestrate calls, which saves time and lowers costs.

Core Features & Use Cases

  • Trigger awareness: Automatically decide when to invoke the decision-agent (new task starts, plan mode needed, or recurring errors).
  • Cost-conscious orchestration: Minimize Opus/agent calls to keep costs predictable.
  • Workflows & architecture: Defines when to spawn the decision-agent and how results are summarized for execution.

Quick Start

When you receive a complex user request, call the Task tool with subagent_type set to "decision-agent" and provide the contextual inputs. After the decision-agent completes, summarize the recommended plan and proceed accordingly.

Frequently Asked Questions about spawn-decision

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

FAQPage Schema
When should I use a decision-agent to automate workflow orchestration?

Use a decision-agent when facing complex judgments about task initiation, plan-mode requests, repeated error cycles, or architecture decisions. It reduces manual orchestration calls and unnecessary costs by automating the logic of when spawning is needed.

How do I spawn a decision-agent for workflow automation?

Call the Task tool with subagent_type set to 'decision-agent' and provide user context and search results as inputs. The decision-agent evaluates whether orchestration is needed and returns a concise outcome summary for execution.

What problems does automating decision-making solve in task orchestration?

Automating decisions eliminates manual bottlenecks in determining when to initiate new tasks or switch to plan mode. It reduces Opus/agent calls, keeps costs predictable, and handles error-resolution workflows without repeated manual intervention.

Can I use a decision-agent to handle repeated error cycles?

Yes. The decision-agent detects recurring error patterns and automatically determines whether to spawn task resolution or escalate to architecture decisions, reducing manual intervention in error-resolution workflows.

What input context should I provide when calling a decision-agent?

Provide user context describing the complex judgment needed and relevant search results. This contextual information allows the decision-agent to reason through task initiation, plan-mode requirements, and architecture decisions accurately.