discover-change
Skill0 starsChanged 7 days agoNo licenceView on GitHub
Discover what a change should do and why, before anything is designed or built - the real problem behind the request, how the domain works in the real world, and several approaches to choose from - and write what was agreed into a change file. Use when the developer brings an idea, a wish or a problem that is not yet clear, or a change larger than a quick fix; when they want to question assumptions or rethink where the project is going; and on "let's think this through", "how should we do this", "what are the options", "I have an idea", "question every assumption".
In this repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- accept-changeSkill
- backlogSkill
- build-changeSkill
- design-changeSkill
- git-commit-messageSkill
- learn-from-sessionsSkill
- nextjs-project-setupSkill
- proposeSkill
- review-changeSkill
- try-changeSkill
- upgrade-dependenciesSkill
The file
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
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.

