agentleFS
Sign inStart free
shyamsridhar123shyamsridhar123/kevin-copilot/.github/skills/lfg/SKILL.md

lfg

Skill7 starsChanged 3 months agoMITView on GitHub

Full autonomous engineering workflow

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ce-explain, ce-handoff and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kieranklaassenSkill

    ce-explain

    Explain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.

    Also in 6 projects that use this

  • kieranklaassenSkill

    ce-handoff

    Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.

    Also in 6 projects that use this

  • +10 more from kieranklaassen

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Optional: If the ralph-loop skill is available, run /ralph-loop-ralph-loop "finish all slash commands" --completion-promise "DONE".

    line 10
  2. Distinctive:

    Start with step 2 now (or step 1 if ralph-loop is available).

    line 40

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CRITICAL: You MUST execute every step below IN ORDER. Do NOT skip any required step. Do NOT jump ahead to coding or implementation. The plan phase (step 2) MUST be completed and verified BEFORE any work begins. Violating this order produces bad output.

  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

    GATE: STOP. Verify that the ce-plan workflow produced a plan file in docs/plans/. If no plan file was created, run /ce-plan $ARGUMENTS again. Do NOT proceed to step 3 until a written plan exists. Record the plan file path — it will be passed to ce-review in step 4.

  3. /ce-work

    GATE: STOP. Verify that implementation work was performed - files were created or modified beyond the plan. Do NOT proceed to step 4 if no code changes were made.

  4. /ce-review mode:autofix plan:<plan-path-from-step-2>

    Pass the plan file path from step 2 so ce-review can verify requirements completeness.

  5. /unslop fix

    Strip AI slop after review fixes land — removes commented-out code, filler comments, stale TODOs.

  6. /observe on the areas of code that were changed — analyze patterns in the modified files to capture what was done and how.
  7. /learn — extract reusable patterns from this session into project instincts.
  8. /compound-engineering-todo-resolve
  9. /compound-engineering-test-browser
  10. /compound-engineering-feature-video
  11. Output <promise>DONE</promise> when video is in PR

Start with step 2 now (or step 1 if ralph-loop is available). Remember: plan FIRST, then work. Never skip the plan.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free