hello-subagent

Orchestrates subagent task delegation with context isolation and two-stage review.

702|99|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/hellowind777/helloagents --skill hello-subagent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hello-subagent
Source: https://github.com/hellowind777/helloagents/tree/main/skills/hello-subagent
Command: npx skills add https://github.com/hellowind777/helloagents --skill hello-subagent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When delegating work to subagents, tasks often fail due to polluted context, unclear boundaries, missing acceptance criteria, or unverified output. This Skill defines a disciplined orchestration protocol so subagents receive only the context they need and their results are reviewed before integration.

Core Features & Use Cases

  • Dispatch Standards: Each subagent receives its task from tasks.md, relevant constraints from the plan package (requirements.md, plan.md, or prd/ files with decisions.md), verification commands, and DESIGN.md excerpts when UI work is involved.
  • Fresh Context Isolation: Subagents start without main-session history, handle a single responsibility, and return only results, evidence, or blockers without wrapping output in outer HelloAGENTS formatting or writing turn-state.
  • Two-Stage Review: The main agent performs a requirements-compliance review followed by a code-quality review with verification commands before proceeding to the next task.
  • Use Case: When parallelizing a feature build across multiple subagents, the main agent assigns non-overlapping files, tracks progress as a controller, and handles BLOCKED reports by adding context, upgrading the model, or splitting the task.

Quick Start

Use the hello-subagent skill to split this feature into independent tasks and dispatch them to subagents with clear acceptance criteria.

Frequently Asked Questions about hello-subagent

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

FAQPage Schema
How do I delegate tasks to subagents in an AI coding workflow?

Assign each subagent a single task from tasks.md plus only the relevant plan constraints and verification commands. Give it fresh context without main-session history, and ensure it returns results, evidence, or blockers rather than final user-facing output.

How to run subagents in parallel without file conflicts?

Partition work so different subagents never modify the same file. The main agent acts as a controller tracking progress, and each subagent keeps a single responsibility with explicit acceptance criteria before dispatch.

When should a task not be delegated to a subagent?

Avoid delegation when the task has low independence, unclear boundaries, or no verifiable acceptance criteria. Tasks tightly coupled to main-session context or requiring continuous user interaction are better handled by the main agent directly.

What should I do when a subagent reports BLOCKED?

Evaluate the blocking reason first, then retry with more context, escalate to a stronger model, or split the task into smaller pieces. Do not force repeated retries with the same approach.

How is subagent output verified before delivery?

Apply a two-stage review: first check requirements compliance against the plan package and tasks.md for missing or extra work, then run verification commands and review code quality. Proceed to the next task only after both stages pass.