agentleFS
cwinvestmentscwinvestments/memstack/skills/familiar/SKILL.md

familiar

Skill425 starsChanged 5 months agoMITView on GitHub

Use when the user says 'dispatch', 'send familiar', 'split task', or needs work split across parallel CC sessions.

3 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When this skill activates, output:

    line 13

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

👻 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

  1. Analyze the task: identify independent sub-tasks that can run in parallel
  2. Determine session count: split into 2-6 sessions based on complexity
  3. 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)
  4. Add coordination notes: specify what each session should NOT touch to avoid conflicts
  5. 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)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.