familiar

Decompose large tasks into parallel CC session prompts with merge order.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/jtucker9/mystuff --skill familiar-jtucker9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: familiar
Source: https://github.com/jtucker9/mystuff/tree/main/skills/familiar
Command: npx skills add https://github.com/jtucker9/mystuff --skill familiar-jtucker9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks large tasks into coordinated CC session prompts and orchestrates parallel sub-tasks to accelerate delivery without conflicts.

Core Features & Use Cases

  • Sub-task decomposition: Analyzes a large assignment and breaks it into independent tasks suitable for parallel CC sessions.
  • Session orchestration: Determines an appropriate number of sessions (2-6) and assigns working directories and goals for each.
  • Coordination prompts: Produces complete prompts for each sub-task including context, acceptance criteria, and merge order to ensure clean integration.
  • Use Case: When given a big project, dispatch familiar tasks to multiple CC sessions to run concurrently and then merge results.

Quick Start

Describe the large task and request 2-6 parallel sub-task prompts.

Frequently Asked Questions about familiar

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

FAQPage Schema
How do I break a large project into parallel sub-tasks for concurrent execution?

Parallel session orchestration decomposes a large assignment into independent sub-tasks, determines 2-6 concurrent sessions, assigns working directories, and specifies merge order for clean integration.

How does parallel session management handle context sharing and merge order?

Parallel session management handles context sharing by generating complete coordination prompts for each sub-task, ensuring clean integration through specified merge orders and acceptance criteria.

What is the best way to automate workflow dispatch for multiple concurrent coding sessions?

Workflow automation dispatches multiple CC sessions by splitting a large task into independent components, assigning goals and working directories, and generating coordination prompts to accelerate delivery.

Can I split a complex assignment into 2 to 6 independent sub-tasks across different sessions?

Yes, you can split a complex assignment into 2 to 6 independent sub-tasks across different sessions. The orchestration determines the appropriate number of concurrent sessions and assigns goals for each.

When should I use parallel session orchestration instead of sequential task execution?

Use parallel session orchestration when a large, complex task can be split into independent components and executed concurrently to accelerate delivery without integration conflicts.

What are the limitations of dispatching parallel sub-tasks for concurrent workflow automation?

A limitation of dispatching parallel sub-tasks is that the large task must be decomposable into independent components; tasks with heavy interdependencies may cause integration conflicts during the merge phase.