Menu

Individual skill

evolve-loop

Autonomous /goal loop that rethinks a project's design and adds features and improvements that can change its behavior, each change recorded and proven. Start it only when the user names evolve-loop.

plugins/reidemeister94/development-skills/skills/evolve-loop/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Evolve loop

Evaluate this project in full, rethink its design and components from first principles, and add the features and improvements that make it more useful, correct, fast, and simple.
Changes can alter logic and results. Each change is deliberate, recorded, and proven. Everything else stays identical.
The arguments of the request can set a theme, a focus, a branch, or extra limits.

Invoking this skill approves the work below within the [unattended-run limits](../../shared/unattended-runs.md).
Work on a new branch, `evolve/loop-YYYY-MM-DD`, unless the arguments name one.
When data matters, use representative dev or staging data. Test data migrations only on disposable databases.
Build what the evidence supports. Write a proposal when a change needs the user's decision: unclear business rules, product scope, breaking changes, migrations of real data, permissions, or higher costs.

## Verification first

Before changing behavior, agree with the user on the [definition of done](../create-test/SKILL.md#definition-of-done) and a proven [regression gate](../create-test/SKILL.md#regression-gate), as an [autonomous run](../create-test/SKILL.md#autonomous-work) requires.