agentleFS
RTekayaRTekaya/app-factory/skills/change/SKILL.md

change

Skill0 starsChanged 31 days agoMITView on GitHub

App Factory — change the scope or design of an app during its build (impact analysis, PRD/UX/architecture/plan revisions by their owners, review, then your approval). Use only when the user types /change.

9 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, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow ../factory/references/change.md with the change request above.

    line 15
  2. Very specific:

    If .workflow/state.json does not exist, this project does not use App Factory yet: say so and suggest /factory.

    line 16

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

/change

Change request: $ARGUMENTS (on hosts that do not substitute this, use the text the user typed after the command).

This command belongs to the App Factory workflow. Its procedure lives in the factory skill, next to this one:

  1. Open ../factory/SKILL.md (relative to this file's folder; in Claude Code: ${CLAUDE_SKILL_DIR}/../factory/SKILL.md) and apply its Golden rules. Its SKILL_DIR is that factory folder.
  2. Follow ../factory/references/change.md with the change request above.
  3. If .workflow/state.json does not exist, this project does not use App Factory yet: say so and suggest /factory.

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.