Familiar
Use when the user says 'dispatch', 'send familiar', 'split task', or needs work split across parallel CC sessions.
Install
$ agentstack add skill-cwinvestments-memstack-familiar ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-cwinvestments-memstack-familiar) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
👻 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 3Level 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)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: cwinvestments
- Source: cwinvestments/memstack
- License: MIT
- Homepage: https://memstack.pro
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.