agentleFS
Fadi88Fadi88/one-man-startup/.claude/skills/gates/SKILL.md

gates

Skill16 starsChanged 17 days agoMITView on GitHub

What each gate level (strict, standard, light) switches on and off, and what never relaxes at any level. Use when setup asks the founder to choose a level, when the level changes, and whenever an agent is unsure whether a step is required.

10 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

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

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    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:

    No unconfirmed assumptions (rule 10), and every rejected idea is recorded (rule 12).

    line 19
  2. Distinctive:

    Light is for throwaway prototypes only: no real users, no real personal data, no payments.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 9 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
<!-- Generated by tools/sync_adapters.py from skills/gates/SKILL.md. Edit the source, not this file. -->

Gate levels

project.toml [gates] level is one of three values. Explain them to the founder in these words, not in your own; a level is what this file says it is.

Never relaxed, at any level

  • Outward steps (deploy, merge, push, publish, send, pay, delete, real data writes) wait for the founder's go, one step at a time (skills/ordered-steps/).
  • Data writes prove themselves and can be undone (skills/safe-data-write/).
  • The commit-msg hook refuses banned characters (skills/commit/).
  • No unconfirmed assumptions (rule 10), and every rejected idea is recorded (rule 12).
  • Free tiers are strict, with tested caps before release.

What changes

strictstandardlight
Requirement row before a changealways, new or citedalways for features; a copy or style fix cites the row of the screen it touchesone row per prototype area, cited in every commit; detail optional
Grilling and readiness gateevery featureevery featurenone
Spec audit (skills/spec-audit/)every featurefeatures touching existing codenone
Security and legal reviewevery feature touching data, money, AI output or claimsonly where the feature's spec flags thembefore any real user or real data
Full sweepbefore every hand-off and every commitbefore every commitbefore every commit
QA reportevery changeevery featurebefore any real user

Light is for throwaway prototypes only: no real users, no real personal data, no payments. Moving from light to anything else means writing the missing requirement rows first.

Recommending

Setup always recommends strict and says what it buys, using the table above. If the founder chooses another level, record the level, the reason and when to revisit it in p1-closed-decisions.md, and the declined recommendation in p1-rejected.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.