feature-coordinate

Coordinate parallel subagents across work units with dependency graphs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nathannorthcutt/jlsm --skill feature-coordinate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-coordinate
Source: https://github.com/nathannorthcutt/jlsm/tree/main/.claude/skills/feature-coordinate
Command: npx skills add https://github.com/nathannorthcutt/jlsm --skill feature-coordinate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates multiple independent work units to run in parallel, coordinating their execution, progress, and completion to accelerate complex feature work while preserving correct dependencies.

Core Features & Use Cases

  • Launches independent work units in parallel and tracks progress.
  • Supports balanced and speed execution strategies with dynamic unblocking.
  • Enforces pre-flight checks, dependency graphs, and finalization (merge/verification).

Quick Start

Start the coordinator for your feature slug to begin parallel execution using balanced or speed mode.

Frequently Asked Questions about feature-coordinate

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

FAQPage Schema
How do I orchestrate parallel subagents to manage independent work units?

You can orchestrate parallel subagents by launching a coordinator that tracks execution, manages dependencies, and dispatches work units across batches. This preserves correct execution order while accelerating complex feature development.

What is the difference between balanced and speed execution strategies for parallel task orchestration?

Balanced and speed execution strategies dictate how parallel work units are processed. Speed mode prioritizes rapid completion, while balanced mode manages resources more evenly, with both supporting dynamic unblocking as dependencies resolve.

Can I run feature development tasks in parallel when they have dependencies?

Yes, you can run feature development tasks in parallel even with dependencies. The coordinator constructs a dependency graph and enforces pre-flight checks to dynamically unblock and dispatch work units as their dependencies are resolved.

How do I finalize and verify parallel work units after batch execution?

To finalize and verify parallel work units, the system enforces finalization steps that include merging completed units and running verification checks. This ensures the orchestrated batches integrate correctly into the feature.

What are the limitations of using parallel execution for complex feature work?

Parallel execution for complex feature work requires strict pre-flight checks and dependency graph construction. If independent work units have unresolved dependencies or fail finalization verification, the batch dispatch and merge process will halt.

Do I need to manually construct dependency graphs for parallel subagent orchestration?

No, you do not need to manually construct dependency graphs. The coordinator automatically builds the dependency graph and enforces dispatch contracts to manage the execution, monitoring, and orchestration of your work units.