medcore-fanout

Dispatch concurrent foreground Agent calls across non-overlapping file lanes in the MedCore monorepo.

2|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-fanout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: medcore-fanout
Source: https://github.com/Globussoft-Technologies/medcore/tree/main/.claude/skills/medcore-fanout
Command: npx skills add https://github.com/Globussoft-Technologies/medcore --skill medcore-fanout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MedCore development often needs several independent fixes or test additions at once, but background agent execution is unreliable in this harness, slowing down multi-scope progress.

Core Features & Use Cases

  • Parallel foreground agent dispatch: Runs multiple agent tool-calls concurrently in a single message while avoiding the broken background-agent path.
  • Non-overlapping lane discipline: Enforces explicit file ownership so agents don’t race on shared files like package manifests or lockfiles.
  • Concurrency-safe commit & push workflow: Uses scoped staging and commit commands plus a mandatory rebase-retry push loop to reduce rejected pushes.
  • Two commit strategies: Supports per-agent commits (default) or a single bundled commit with staging-only behavior.
  • E2E/Test backlog and multi-bug closure: Ideal for closing multiple route gaps, generating multiple test files, or addressing multiple independent bugs in one batch.

Quick Start

Invoke medcore-fanout when you want to close several independent MedCore gaps in parallel (for example, “fan out and add E2E coverage for these 4 different routes, each in its own spec file”).

Frequently Asked Questions about medcore-fanout

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

FAQPage Schema
How do I run parallel agent tasks in a monorepo without file lock races?

Parallel agent tasks in a monorepo require dispatching concurrent foreground calls that target non-overlapping file lanes to avoid races on shared files like package.json or lockfiles.

What is the best way to batch multiple independent bug fixes concurrently?

Batching multiple independent bug fixes concurrently is best done by dispatching parallel foreground agent calls across non-overlapping files, ensuring scoped git add and commit operations for each lane.

How do I safely commit and push multiple parallel changes in a monorepo?

To safely commit and push parallel changes in a monorepo, use scoped staging with file-level scoping and a mandatory rebase-retry push loop to reduce rejected pushes from concurrent updates.

Can I generate multiple E2E test spec files in parallel for different routes?

Generating multiple E2E test spec files in parallel is supported by dispatching concurrent agent tasks, where each agent independently handles a specific route's coverage in its own file lane.

Why do background agent executions fail when running multiple concurrent tasks?

Background agent execution is unreliable in the harness, slowing multi-scope progress, so dispatching concurrent foreground agent calls is required to execute parallel tasks safely.

Does parallel agent dispatch support a single bundled commit instead of per-agent commits?

Parallel agent dispatch supports a single bundled commit with staging-only behavior as an alternative to the default per-agent commit strategy, allowing flexible monorepo git workflow management.