subagent

Execute delegated subagent tasks with pull, plan, execute, verify, commit, and push.

4|2|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/skills-catalog --skill subagent-all-the-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent
Source: https://github.com/All-The-Vibes/skills-catalog/tree/main/.claude/skills/core/subagent
Command: npx skills add https://github.com/All-The-Vibes/skills-catalog --skill subagent-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables subagents to take delegated tasks from a tech lead and deliver work that is done, clean, and ready for integration, reducing miscommunication and rework.

Core Features & Use Cases

  • Diligent execution: follow the task spec and hygiene standards to ensure the work meets acceptance criteria.
  • Plan, execute, verify: read context, plan changes, implement, verify, and document results.
  • Use Case: as a subagent, you receive a delegation prompt and must deliver final changes that are merged and pushed to remote.

Quick Start

Use the subagent skill to complete a delegated task following the execution protocol described in the Skill's body, including pulling, planning, executing, and pushing to remote.

Frequently Asked Questions about subagent

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

FAQPage Schema
How do I automate delegated task execution for subagents to ensure merge-ready changes?

Automating delegated task execution involves a mandatory protocol where subagents pull first, plan changes, execute, verify, and push. This enforces hygiene and traceability, producing stable, merge-ready results for tech-lead driven workflows.

What is the standard execution protocol for multi-agent workflows to maintain git hygiene?

The standard execution protocol for multi-agent workflows requires pulling context, planning changes, implementing, verifying, and pushing to remote. This ensures subagents deliver clean, verifiable changes that meet acceptance criteria and hygiene standards.

How do subagents handle task delegation and backlog synchronization in software engineering?

Subagents handle task delegation by reading the scoped context, following the task spec, and executing changes. Backlog synchronization is enforced during the process to maintain traceability and ensure the delivered work is ready for integration.

Does the subagent workflow require a tech lead to scope tasks before execution?

Yes, the subagent workflow applies to tech-lead driven multi-agent environments. A tech lead must provide a clearly scoped delegation prompt so the subagent can follow the execution protocol and deliver verifiable, merge-ready changes.

What's the best way to ensure subagent changes are stable and ready for remote integration?

The best way to ensure stable changes is following the mandatory execution protocol: pull first, plan, execute, verify, and commit. This enforces hygiene and traceability, guaranteeing the subagent's work is merge-ready and pushed to remote.

Why does delegated task execution fail to produce verifiable results without an execution protocol?

Delegated task execution fails without a protocol because it lacks mandatory hygiene, traceability, and verification steps. Enforcing a pull, plan, execute, verify, and push sequence ensures subagents deliver clean work that meets acceptance criteria.