Skill

familiar

Splits large tasks into 2-6 coordinated prompts for parallel CC sessions, including sub-task analysis, shared context, conflict avoidance, and merge order.

developer-tools

automation

npx claudepluginhub cwinvestments/memstack --plugin memstack

Tool Access

This skill uses the workspace's default tool permissions.

Preview

*Break large tasks into coordinated CC session prompts for parallel execution.*

SKILL.md

Similar Skills

subagent-driven-development

Dispatches subagents via Claude Code's Agent tool to parallelize 3+ independent tasks across different files/modules with verification commands. Activates on execution-ready plans or keywords like 'use subagents'.

claudekit

dispatching-parallel-agents

Provides patterns for subagent delegation and parallel execution using fan-out/fan-in, map-reduce, and isolation techniques. Use for independent subtasks, multi-area research, coordinated specialist work, or avoiding sequential delays.

5 files1 tool

playbooks-virtuoso

divide-and-conquer

Executes tasks from taskmd files by splitting into independent workstreams run in parallel via subagents. Manages progress, worklogs, planning, coordination, tests, and integration for maximum concurrency.

9 tools

taskmd-lite

Stats

Stars307

Forks28

Last CommitApr 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

👻 Familiar — Dispatching Sub-Agents...

Break large tasks into coordinated CC session prompts for parallel execution.

Activation

When this skill activates, output:

👻 Familiar — Dispatching sub-agents...

Then execute the protocol below.

Protocol

Analyze the task — identify independent sub-tasks that can run in parallel

Determine session count — split into 2-6 sessions based on complexity

For each sub-task, generate a complete CC prompt that includes:

Working directory path
Full task description with acceptance criteria
Any shared context (database schema, API contracts, types)
MemStack activation line: Read $MEMSTACK_PATH/MEMSTACK.md
CC Monitor reporting snippet (if configured in config.json)

Add coordination notes — specify what each session should NOT touch to avoid conflicts

Define merge order — which session's work should be committed first

Inputs

The large task description

Project directory from config.json

Number of available CC sessions (default: 3)

Outputs

Numbered list of sub-task prompts, each ready to paste into a new CC session

Coordination notes explaining dependencies and merge order

Example Usage

User: "dispatch — build the analytics dashboard, API routes, and database migration"

Familiar activates:

👻 Familiar — Dispatching sub-agents... Session 1 — Database & Types Working directory: C:\Projects\AdminStack Task: Create migration + TypeScript types for analytics... Session 2 — API Routes Working directory: C:\Projects\AdminStack Task: Build /api/analytics endpoints (types from Session 1)... Session 3 — Frontend Page Working directory: C:\Projects\AdminStack Task: Build /analytics dashboard page... Merge order: Session 1 → Session 2 → Session 3

Level History

Lv.1 — Base: Multi-agent dispatch with coordinated prompts. (Origin: MemStack v1.0, Feb 2026)

Lv.2 — Enhanced: Added YAML frontmatter, activation message, merge ordering. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)