delegation-principle

Delegate implementation tasks to subagents within CURDX workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ForeverWorld/curdx-ralph --skill delegation-principle-foreverworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegation-principle
Source: https://github.com/ForeverWorld/curdx-ralph/tree/main/skills/delegation-principle
Command: npx skills add https://github.com/ForeverWorld/curdx-ralph --skill delegation-principle-foreverworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents the main agent from performing implementation work directly and enforces a coordination-only role so changes are made by specialized subagents with clear responsibilities and traceability.

Core Features & Use Cases

  • Coordinator-only workflow: The agent parses intent, reads state, and issues Tasks rather than editing files or running commands.
  • Delegation enforcement: Requires use of the Task tool with appropriate subagent_type and full context to ensure subagents perform implementation, research, or design.
  • Auditability and safety: Keeps a clean separation of responsibilities so every change traces to a Task and subagent, supporting review and guardrails.
  • Use Case: In CURDX pipelines, use this Skill when converting user requests into actionable Tasks for product-manager, architect-reviewer, task-planner, or spec-executor subagents.

Quick Start

Delegate the implementation by creating a Task for a spec-executor subagent that includes the full state context and wait for the subagent to complete before reporting results.

Frequently Asked Questions about delegation-principle

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

FAQPage Schema
How do I delegate implementation work to subagents instead of editing files directly?

Delegation to subagents involves using the Task tool with the appropriate subagent_type and full context. The coordinator agent parses user intent, reads state files, and creates Task requests while waiting for subagent completion.

What is a coordinator-only workflow for agent task delegation?

A coordinator-only workflow restricts the main agent to state management and delegation. The agent parses intent, reads state, and issues Tasks to specialized subagents rather than performing direct code changes, ensuring traceability.

How do I maintain auditability and safety when managing subagent tasks?

Auditability and safety are maintained by enforcing a strict separation of responsibilities. Every code change must trace to a Task request and subagent, keeping the coordinator restricted to state management while delegating implementation work.

Can I use subagent delegation for research and design tasks in CURDX pipelines?

Yes, subagent delegation applies within CURDX workflows for research, requirements, design, planning, and execution. You convert user requests into actionable Tasks for product-manager, architect-reviewer, task-planner, or spec-executor subagents.

Why does the coordinator agent need to pass complete context to subagents?

Passing complete context to subagents ensures specialized agents have the necessary state and intent to perform implementation safely. This delegation enforcement prevents incomplete task execution and preserves operational guardrails.

What are the limitations of restricting the main agent to a delegation-only role?

The coordinator cannot perform direct code edits or run commands directly. It is limited to parsing intent, reading state files, and creating Task tool requests, meaning all implementation must wait for subagent completion.