driver-as-in-adam

Orchestrate parallel mule agents in isolated workspaces for Linear issues.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ships/eden --skill driver-as-in-adam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: driver-as-in-adam
Source: https://github.com/ships/eden/tree/main/assets/claude/skills/driver-as-in-adam
Command: npx skills add https://github.com/ships/eden --skill driver-as-in-adam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

ADAM orchestrates multiple subordinate “mule” agents in parallel while keeping their instructions dense and constrained, so complex multi-part engineering work can be executed efficiently and consistently.

Core Features & Use Cases

  • Parallel multi-agent orchestration: Spawns multiple mules via Claude Code’s Task tool, each in an isolated workspace directory.
  • Instruction density discipline: Converts driver intent into lean, imperative, structured prompts using the provided instruction-density guidance.
  • Linear issue workflow integration (field updates only): Fetches issues, assigns to the correct user, and updates status via MCP tools while explicitly avoiding Linear comments.
  • Workspace lifecycle & tracking: Maintains /Users/eve/workspace/AGENTS/MULES.md as the single source of truth and archives completed or orphaned workspaces.

Quick Start

Ask an AI agent to run the ADAM driver to manage parallel work on multiple Linear issues (e.g., “Adam, coordinate mules to fix LINEAR-123 and LINEAR-456 in parallel, update their assignees/statuses, and report commit SHAs plus PR URLs when done”).

Frequently Asked Questions about driver-as-in-adam

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

FAQPage Schema
How do I coordinate parallel agents to work on multiple Linear issues simultaneously?

Instruction density discipline converts driver intent into lean, imperative, structured prompts, ensuring subordinate agents receive constrained, unambiguous directives that minimize deviation and maximize execution efficiency during parallel task completion.

How do I track the lifecycle of isolated git workspaces during parallel task execution?

Workspace lifecycle tracking maintains a MULES.md file as the single source of truth for active workspaces, applying git-safe execution patterns and archiving completed or orphaned directories to ensure clean repository state after parallel agent tasks finish.

Can I update Linear issue statuses and assignees without posting comments during parallel agent orchestration?

Parallel multi-agent orchestration requires Claude Code Task-based spawning for subordinate agents, git branches for isolated workspace execution, and Linear MCP for issue retrieval and status updates to successfully coordinate concurrent engineering work.

What is the best way to manage parallel git branches across multiple concurrent engineering tasks?

Managing parallel git branches is achieved by allocating isolated workspace directories to each subordinate agent, applying git-safe execution patterns to prevent conflicts, and tracking all active branches within a centralized MULES.md workspace file.