agentleFS
n1m21nn1m21n/Infinite/.claude/skills/infinite-lifecycle/SKILL.md

infinite-lifecycle

Skill281 starsChanged 19 days agoLicence not identifiedView on GitHub

The process the owner and every agent follow on Infinite: three loops (quality, build, rule), 12 build stages with gates, lanes with a done check each (code and non-code), session claims, who decides what when the owner is away, and which rule wins. Use at the start of every session and every new ask (read docs/NOW.md first), whenever a decision has to be made without the owner, when unsure which skill or lane applies, when a gate fails, after a release, and monthly for the rule audit.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.