Systematic debug workflow: research → orchestrate agents → escalate. Suggest when: stuck after 2-3 attempts, unfamiliar tooling, tempted to "try random things", or errors don't match documentation.
Fan one task out to multiple independent lionagi workers through `fanout.submit`, optionally synthesizing their answers. Use when several parallel perspectives can work without dependency handoffs.
Plan and run a dependency-aware lionagi DAG through `flow.submit`, including dry runs and reactive follow-up capacity. Use when work has stages, dependencies, parallel branches, or a final synthesis step.
Plan and execute multi-agent workflows through lionagi's orchestration MCP tool: flow.submit (DAG pipelines), fanout.submit (parallel workers), agent.submit (one agent), and play.submit (saved playbooks). Use when a task needs multiple agents working in…
Run an existing lionagi playbook through the orchestration MCP server and retrieve its background result. Use when a saved `.playbook.yaml` workflow should be executed with concrete input or declared arguments.
Author lionagi playbooks — reusable YAML workflow templates that define parametric agent tasks. Playbooks live at ~/.lionagi/playbooks/ and run via the `play.submit` MCP verb (or `li play <name>` from a lionagi checkout). Use when: creating reusable…
Multi-perspective PR review procedure. Plan a minimal DAG of specialists scoped to what the PR actually touches, synthesize with a critic, post ONE consolidated comment per verbosity tier. Pull before any structured PR review so the methodology stays…
General-purpose code review checklist. Use when reviewing any code change without a narrower specialization. Complements security-review, pr-review (multi-perspective), and the other review skills — pull this when you need the standard correctness/quality…