lfx-coordinator

Coordinate development across LFX repositories by delegating tasks to specialized skills.

8|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-coordinator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lfx-coordinator
Source: https://github.com/linuxfoundation/lfx-skills/tree/main/lfx-coordinator
Command: npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-coordinator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill orchestrates end-to-end development across multiple LFX repos by delegating code changes to specialized skills rather than writing code itself.

Core Features & Use Cases

  • Cross-repo coordination: auto-detects context and routes tasks to /lfx-backend-builder and /lfx-ui-builder.
  • Governance and planning: creates a delegation plan, validates prerequisites, and tracks progress.
  • End-to-end execution: coordinates research, planning, build, and validation steps while summarizing results.

Quick Start

Describe the feature or bug you want to implement to start the coordination workflow.

Frequently Asked Questions about lfx-coordinator

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

FAQPage Schema
How do I coordinate cross-repo development workflows across backend and frontend?

Cross-repo development workflows are coordinated by auto-detecting repository context and routing tasks to specialized skills, creating a delegation plan with ownership, and validating execution steps.

What is the best way to orchestrate feature implementation across multiple repositories?

Orchestrating multi-repo features is handled by delegating code changes to specialized builder skills rather than writing code directly, tracking end-to-end progress from research to validation.

Can I use this coordinator to fix bugs spanning both backend and UI repositories?

Yes, fixing bugs across backend and UI repositories is supported by delegating changes to respective builder skills after validating prerequisites and generating an ownership delegation plan.

How does multi-repo workflow orchestration validate prerequisites before execution?

Multi-repo orchestration validates prerequisites by generating a delegation plan that defines ownership and tracks validation steps before routing delegated changes to specialized skills.

Do I need to manually specify repository context for cross-repo refactoring tasks?

No, cross-repo refactoring tasks do not require manual context specification because the workflow auto-detects repository context to route changes to the appropriate backend and UI skills.