agentleFS
akimisri17akimisri17/idea-to-app-kit/.agents/skills/new-idea/SKILL.md

new-idea

Skill0 starsChanged 40 days agoMITView on GitHub

Weighs a new idea or feature request before anything is built, so the plan doesn't grow by accident. Use when the person says "can we also add…", "what if it could…", "one more thing…", or asks for something not in docs 1–2.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Not doing: add it there with the reason.

    line 25
  2. Distinctive:

    add it to doc 1 (an R# with a "Done when" and the M# it serves), then doc 2, then doc 3 if it adds data, steps or permissions.

    line 29
  3. Distinctive:

    put it in a wave in doc 5.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 5 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

New idea

  1. Restate the idea in one sentence, and the problem it solves for which person.
  2. Check it against the plan (doc 1):
    • Is it under "Not doing"? If so, say so and quote the reason.
    • Does it break anything under "Must never happen"?
    • Which metric (M#) would it move? If none, say so plainly.
  3. Give the strongest reason not to do it (or not yet), from these:
    • it delays something already promised;
    • it adds a screen, a role, data or cost to maintain;
    • an existing tool already does it;
    • there's no evidence anyone needs it.
  4. Size it:
    • small (a tweak inside an existing screen),
    • medium (a new screen or rule), or
    • large (new data, roles or a service).
  5. Recommend one:
    • Now: a Must that serves a metric.
    • Later: goes in a later wave.
    • Not doing: add it there with the reason.
    • Small tweak: just do it and note it in the handoff.
  6. Reply in the answer-first shape (AGENTS.md) and wait for the person's OK.
  7. If approved:
    • add it to doc 1 (an R# with a "Done when" and the M# it serves), then doc 2, then doc 3 if it adds data, steps or permissions;
    • put it in a wave in doc 5;
    • run sh tools/check-plan.sh.

Adapted from pm-toolkit by Martin Foerster (MIT). See THIRD_PARTY_NOTICES.md.

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.