Swarm-enabled version of LFG, running tasks in parallel for faster autonomous engineering.

Install

mkdir -p .claude/skills/slfg-all-the-vibes && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18726" && unzip -o skill.zip -d .claude/skills/slfg-all-the-vibes && rm skill.zip

Installs to .claude/skills/slfg-all-the-vibes

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Full autonomous engineering workflow using swarm mode for parallel execution
76 charsno explicit “when” trigger
Advanced

Key capabilities

  • Orchestrate sub-agents for parallel task execution
  • Maintain central state for resumability
  • Ensure safe concurrent writes during parallel phases
  • Orchestrate `ce-plan`, `ce-work`, `ce-review` phases in swarm mode

How it works

The skill uses a state helper to track phase completion and artifacts, orchestrating sub-agents in parallel during specific phases while ensuring only the parent records the state to prevent race conditions.

Inputs & outputs

You give it
A feature description
You get back
A completed feature with a plan, implementation, and review artifacts, generated in parallel

When to use slfg

  • Parallelize multi-step engineering tasks
  • Improve development speed
  • Orchestrate swarm-based automation

About this skill

Swarm-enabled LFG. Run these steps in order, parallelizing where indicated. Do not stop between steps — complete every step through to the end.

Run State (resumability + artifact passing)

This workflow is resumable. A tiny helper tracks which phases are done and where each phase's output lives, so re-invoking /slfg continues from the first unfinished phase instead of restarting.

  • Helper: node .github/hooks/scripts/lfg-state.js — commands init, bind-plan, done <phase> --run-id <id> [--artifact <repo-relative-path>], status --run-id <id>, run-id-from-plan --plan <path>. It writes .atv/runs/<run-id>/ (gitignored, local-only).
  • On start: derive RUN_ID from an existing docs/plans/ plan via run-id-from-plan, else init a provisional id. Run node .github/hooks/scripts/lfg-state.js status --run-id <RUN_ID> and skip phases already done.
  • Pass run:<RUN_ID> to every sub-skill so artifacts co-locate and downstream phases read paths, not full content.
  • PARENT-ONLY WRITES (concurrency safety): during the Parallel Phase, swarm subagents MUST NOT write run state. Each subagent only returns its artifact path; the parent orchestrator records each node .github/hooks/scripts/lfg-state.js done <phase> --run-id <RUN_ID> --artifact <path> after the parallel agents join. This avoids races on the state directory.
  • Re-entry safety: ce-work MUST run with mode:orchestrated so resume reconciles existing work instead of duplicating commits/PRs. If .atv/runs/ is absent, infer progress from the plan, branch, and any open PR.

Sequential Phase

  1. Optional: If the ralph-loop skill is available, run /ralph-loop-ralph-loop "finish all slash commands" --completion-promise "DONE". If not available or it fails, skip and continue to step 2 immediately.
  2. /ce-plan $ARGUMENTS run:<RUN_ID>Record the plan file path from docs/plans/ for steps 4 and 6. Then (parent) node .github/hooks/scripts/lfg-state.js bind-plan --run-id <RUN_ID> --plan <plan-path> and node .github/hooks/scripts/lfg-state.js done ce-plan --run-id <RUN_ID> --artifact <plan-path>.
  3. /ce-work mode:orchestrated plan:<plan-path-from-step-2> run:<RUN_ID>Use swarm mode: Make a Task list and launch an army of agent swarm subagents to build the plan. Then (parent) node .github/hooks/scripts/lfg-state.js done ce-work --run-id <RUN_ID>.

Parallel Phase

After work completes, launch steps 4 and 5 as parallel swarm agents (both only need code to be written). Subagents return artifact paths only — the parent records state after they join:

  1. /ce-review mode:report-only plan:<plan-path-from-step-2> run:<RUN_ID> — spawn as background Task agent
  2. /compound-engineering-test-browser run:<RUN_ID> — spawn as background Task agent

Wait for both to complete before continuing. Then (parent) node .github/hooks/scripts/lfg-state.js done test-browser --run-id <RUN_ID> --artifact <report-path>.

Autofix Phase

  1. /ce-review mode:autofix plan:<plan-path-from-step-2> run:<RUN_ID> — run sequentially after the parallel phase so it can safely mutate the checkout, apply safe_auto fixes, and emit residual todos for step 7. Then (parent) node .github/hooks/scripts/lfg-state.js done ce-review --run-id <RUN_ID> --artifact <review-artifact-path>.

Finalize Phase

  1. /compound-engineering-todo-resolve — resolve findings, compound on learnings, clean up completed todos. Then node .github/hooks/scripts/lfg-state.js done todo-resolve --run-id <RUN_ID>.
  2. /compound-engineering-feature-video — record the final walkthrough and add to PR. Then node .github/hooks/scripts/lfg-state.js done feature-video --run-id <RUN_ID>.
  3. Output <promise>DONE</promise> when video is in PR

Start with step 1 now.

When not to use it

  • When subagents write run state directly during parallel phases
  • When re-entering non-`done` phases without `mode:orchestrated`

Limitations

  • Requires parent orchestrator to record state after parallel agents join
  • Requires `ce-work` to run with `mode:orchestrated` for re-entry safety
  • Subagents must not write run state during the Parallel Phase

How it compares

This skill extends the autonomous engineering workflow by enabling parallel execution of tasks using swarm agents, significantly reducing wall-clock time compared to sequential execution.

Compared to similar skills

slfg side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
slfg (this skill)01moNo flagsAdvanced
lfg01moNo flagsIntermediate
workflow-automation35moReviewIntermediate
workflow-execute13moReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

lfg

All-The-Vibes

Full autonomous engineering workflow

00

workflow-automation

ruvnet

Workflow creation, execution, and template management. Automates complex multi-step processes with agent coordination. Use when: automating processes, creating reusable workflows, orchestrating multi-step tasks. Skip when: simple single-step tasks, ad-hoc operations.

327

workflow-execute

catlog22

Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking. Triggers on "workflow execute".

13

gsd-execute-phase

AcidicSoil

Execute all plans in a phase with wave-based parallelization

00

opencode-cli

SpillwaveSolutions

This skill should be used when configuring or using the OpenCode CLI for headless LLM automation. Use when the user asks to "configure opencode", "use opencode cli", "set up opencode", "opencode run command", "opencode model selection", "opencode providers", "opencode vertex ai", "opencode mcp servers", "opencode ollama", "opencode local models", "opencode deepseek", "opencode kimi", "opencode mistral", "fallback cli tool", or "headless llm cli". Covers command syntax, provider configuration, Vertex AI setup, MCP servers, local models, cloud providers, and subprocess integration patterns.

14174

claude-automation-recommender

anthropics

Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.

47140

Search skills

Search the agent skills registry