agentleFS
neuraforge-cl-esneuraforge-cl-es/adaptive-engineering/skills/minimal-planning/SKILL.md

minimal-planning

Skill1 starsChanged 12 days agoMITView on GitHub

Produce a right-sized implementation plan with acceptance criteria, complexity budget, verification, and rollback proportional to the selected mode.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a short plan containing:

    line 13
  2. Distinctive:

    Add only the rigor the risk requires:

    line 21
  3. Distinctive:

    test and operational verification strategy

    line 27

≈ “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

Minimal Planning

Plan only enough to reduce execution risk.

FAST

Usually no formal plan. If needed, use at most three execution bullets.

STANDARD

Create a short plan containing:

  1. acceptance criteria
  2. files/components expected to change
  3. implementation sequence (normally 3-7 steps)
  4. targeted tests/verification
  5. complexity budget

DEEP

Add only the rigor the risk requires:

  1. requirements and invariants
  2. failure modes
  3. considered approaches and selected trade-off
  4. staged implementation
  5. data/compatibility/rollback considerations
  6. test and operational verification strategy
  7. explicit complexity budget

Rule

A plan must make implementation easier. If a plan repeats the request without resolving uncertainty, shorten it or investigate instead.

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.