agentleFS
malinskibeniaminmalinskibeniamin/skills/plow-ahead/SKILL.md

plow-ahead

Skill4 starsChanged 12 days agoMITView on GitHub

Continue through routine ambiguity using reversible assumptions. Use when the user says plow ahead, keep going, use your judgment, or do not stop until done.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Read references/builder-upstream.md.

    line 6
  2. Distinctive:

    Prefer local, reversible, low-blast changes.

    line 11
  3. Distinctive:

    Start with smallest meaningful test.

    line 14
  4. Distinctive:

    When close, choose reviewer clarity.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Read references/builder-upstream.md. Continue through normal uncertainty.

Decide

  1. Reuse repo patterns.
  2. Prefer local, reversible, low-blast changes.
  3. Keep request scope.
  4. Choose correct/maintainable over clever.
  5. Start with smallest meaningful test; broaden by risk.
  6. When close, choose reviewer clarity.

Stop only for true blockers

Missing access/credentials/private data; unrequested destructive/irreversible/production/history rewrite; irreducible legal/privacy/security/compliance risk; user-reserved decision; repeated verification failure where next fix is speculative/broad.

Loop

Set criteria/assumptions; inspect files/docs/issue/PR/visual/runtime; implement coherent slices; validate and repair; review against request; report decisions, changes, evidence, residual risk, next action.

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.