subagent-workflow

Name: subagent-workflow
Availability: InStock
Author: discountedcookie

Coordinate subagent orchestration with session tracking and structured handoffs.

Updated Oct 26, 2025

Search Tags:#subagents #orchestration #coordination #handoff #session-management

Ready to run

npx skills add https://github.com/discountedcookie/10x-mapmaster --skill subagent-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subagent-workflow
Source: https://github.com/discountedcookie/10x-mapmaster/tree/main/.opencode/skills/subagent-workflow
Command: npx skills add https://github.com/discountedcookie/10x-mapmaster --skill subagent-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates subagents for implementation, including session tracking and handoffs.

Core Features & Use Cases

Session management: Track and recall subagent sessions for follow-ups.
Dispatch patterns: Clear rules for when to fresh-dispatch vs recall.
Handoff: Structured patterns for cross-domain coordination.

Quick Start

Dispatch a subagent with a scoped task and record the session_id for follow-up questions.

Frequently Asked Questions about subagent-workflow

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

FAQPage Schema

How do I coordinate multiple specialized agents on a single project?▼

Subagent orchestration manages task delegation across specialized agents like frontend experts, code reviewers, and researchers. Dispatch each agent with a scoped task, record the session ID, and use structured handoff patterns to maintain context continuity across domains.

What's the best way to track agent sessions for follow-up questions?▼

Session management records each subagent dispatch with a unique session_id. On follow-ups, recall the agent with the recorded session ID to restore context and continue work without restarting, ensuring continuity across multi-turn interactions.

How do I hand off work between different specialized agents?▼

Structured handoff patterns use explicit TASK/CONTEXT/CONSTRAINTS formatting to pass state between agents. Sequential handoff ensures the receiving agent has full context from the previous agent's work and can continue seamlessly.

Can I use session tracking to recall agent work on follow-up requests?▼

Yes. Session IDs enable recall-based handoffs where follow-up questions automatically reconnect to the prior agent with full context restored. This eliminates redundant setup and maintains reasoning continuity across multiple interactions.

When should I dispatch a fresh agent versus recalling an existing session?▼

Dispatch fresh when starting a new, unrelated task. Recall when the work is a continuation or refinement of a prior session. Clear dispatch rules prevent context loss and ensure efficient agent utilization across related subtasks.

How do I verify work completed by a subagent?▼

Post-subagent verification workflows inspect outputs against original requirements. This step catches misalignments early and confirms the agent satisfied functional and technical constraints before proceeding to the next handoff.