mlld:llm-first

Replace hard-coded branching with prompt-driven decision orchestration in mlld pipelines.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mlld-lang/mlld --skill mlld-llm-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mlld:llm-first
Source: https://github.com/mlld-lang/mlld/tree/main/plugins/mlld/skills/llm-first
Command: npx skills add https://github.com/mlld-lang/mlld --skill mlld-llm-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LLM-first design principles address the problem of brittle, hard-coded orchestration by shifting decision-making from code into prompts, enabling adaptive and auditable pipelines.

Core Features & Use Cases

  • Guidance-driven decisions: prompts determine actions based on context, reducing code complexity.
  • Clear context management: promotes consistent state representation and phase transitions without embedding logic.
  • Reusable decision templates: supports iterative loops and safe guardrails by externalizing strategy to prompts.

Quick Start

Describe how to apply LLM-first design to mlld pipelines to replace hard-coded decisions with prompt-driven guidance.

Frequently Asked Questions about mlld:llm-first

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

FAQPage Schema
What is prompt-driven orchestration in LLM pipelines?

Prompt-driven orchestration shifts rigid decision logic from hard-coded branches into LLM prompts, enabling adaptive and auditable pipelines. This approach uses guidance to determine actions based on context, reducing code complexity.

How do I replace hard-coded branching with prompts in mlld pipelines?

To replace hard-coded branching in mlld pipelines, externalize strategy into reusable decision templates and iterative loops. This applies LLM-first design principles to determine actions based on context without embedding logic.

Can I manage context state and phase transitions without embedding logic?

Yes, LLM-first orchestration promotes consistent state representation and phase transitions through clear context management. This externalizes logic to prompts, ensuring state is managed without embedding hard-coded rules.

What is the best way to handle iterative decision prompts across diverse edge cases?

The best way to handle diverse edge cases is using reusable decision templates with safe guardrails. This externalizes strategy to prompts, supporting iterative loops while avoiding rigid, hard-coded decision logic.

Does LLM-first orchestration require specific decision schemas?

Yes, LLM-first orchestration specifies requirements for prompts, context conventions, and decision schemas. These schemas ensure safe guardrails and structured actions, replacing hard-coded branching with prompt-driven guidance.

When should I not use prompt-driven orchestration for pipelines?

You should not use prompt-driven orchestration when workflows require deterministic execution without context evaluation. This approach shifts decision-making into prompts, which introduces non-determinism unsuitable for rigid, hard-coded paths.