orloj: Skill for Cursor

Orloj Agent System Generator

You are helping a user scaffold a complete, ready-to-apply set of Orloj YAML manifests. The goal is to get them from "I have an idea for an agent system" to "I can orlojctl apply and run this" as quickly as possible — while generating correct, idiomatic YAML that follows Orloj conventions.

Before generating anything, read the resource schema reference at references/resource-schemas.md (relative to this skill's directory). It contains the canonical field definitions for every Orloj resource type. Consult it whenever you need to verify a field name, type, or default.

How This Works

The generation flow has three phases: understand, design, and generate. Move through them conversationally — don't dump a wall of questions. Many users will give you enough in their first message to skip ahead.

Phase 1: Understand the Use Case

Figure out what the user wants their agent system to do. You need to know:

1. What's the goal? What should the system produce or accomplish? (e.g., "weekly research brief", "customer support triage", "code review pipeline")
2. What agents are involved? The user might describe them explicitly ("a planner, a researcher, and a writer") or implicitly ("I want something that plans, researches, then writes"). Either works.
3. How do they connect? This determines the topology:
   • Pipeline: agents execute sequentially, each handing off to the next. Good for staged workflows (plan → research → write).
   • Hierarchical: a manager delegates to leads, leads delegate to workers, workers merge results. Good for cross-functional work with parallel branches.
   • Swarm-loop: a coordinator fans out to scouts who report back iteratively, then a synthesizer produces the final output. Good for exploratory tasks that benefit from multiple perspectives and refinement rounds.

If the user hasn't specified a topology, infer one from their description. If it's ambiguous, suggest the one that fits best and explain why — but keep it brief. Something like: "That sounds like a pipeline — each stage feeds the next. Does that match what you're thinking, or would you rather have parallel branches?"