Familiar
ProductivityfamiliarFamiliar is an Agent Skill for productivity published in the cwinvestments/memstack repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when the user says 'dispatch', 'send familiar', 'split task', or needs work split across parallel CC sessions.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/cwinvestments/memstack/blob/HEAD/skills/familiar/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/familiar, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
š» 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)