agentleFS
nrjdalalnrjdalal/zerostarter/.agents/skills/icebox/SKILL.md

icebox

Skill65 starsChanged 16 days agoMITView on GitHub

Icebox a raised-but-undecided concern instead of forcing a plan-or-dismiss call: record it with no verdict so the context survives. Use when a review, PR, audit, or eval surfaces something real-maybe that should not be scheduled or closed yet, or when the user says to icebox or park an item.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Write the concern to .github/notes/plans/<slug>.md, or append a section to a fitting file: state the concern, its context, and the open …

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Icebox

Some concerns are real yet not decidable right now. Forcing one into a plan overstates it; closing it loses the context. Ice is the third option: park the concern verbatim, with no verdict, until someone can rule on it. It sits between the plans backlog and a closed issue. The full definition and the standing index live in .github/notes/plans/README.md.

What belongs on ice

Ice is only for the genuinely undecided, all three at once:

  • Raised by a review note, a PR follow-up, or an audit or eval finding.
  • Not schedulable into the plans backlog, because no next action is agreed.
  • Not resolvable as fix-it or not-a-problem with any confidence.

A known next action belongs in the plans backlog; a confident verdict gets shipped or closed. Everything else waits on ice until it thaws into one of those.

Park it

  1. Write the concern to .github/notes/plans/<slug>.md, or append a section to a fitting file: state the concern, its context, and the open question, with no plan and no verdict. Done when a reader grasps what is unresolved and finds no recommendation.
  2. Link it under ## Icebox in .github/notes/plans/README.md. Done when the index points at the file.
  3. Mirror the one-liner and the plans/<slug>.md path as an unchecked box on the standing Icebox issue (#707). Done when gh issue view 707 shows it.

Thaw

An item leaves ice only by being decided. When that happens, check its box in #707, record the outcome (shipped, dismissed, or moved to the backlog), and graduate its write-up to the plans backlog or delete it.

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.