agentleFS
Sign inStart free
veraetogrex-portfolioveraetogrex-portfolio/solo-sdd/skills/changes/SKILL.md

changes

Skill0 starsChanged yesterdayMITView on GitHub

Use only when the user explicitly invokes /changes - "what is in specs 16 to 47?", "what about 25, 37 and 73", "which specs are free", "which changes are ready for the archive", "show all changes".

4 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    If the user in reply marks changes as ready ("16 is ready, 26 is ready"), close each through /spec-next with a check, not by a plain move …

    line 29

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

changes: a table of change states

Argument (optional): a range (16-47), numbers (25 37 73) or a name. Without an argument, all open changes. Read only.

Order

  1. solo-sdd list --json and the folder names in solo-sdd/changes/archive: look for the numbers from the argument in both places.
  2. For every change:
    • state: open | archived (date) | not found;
    • tasks: done of total (- [x] and - [ ] in tasks.md);
    • CLAIM: who and how many hours ago;
    • WAITING: the condition;
    • unarchived changes from Depends On;
    • the last change: git log -1 --format=%cr -- <folder>.
  3. A table in number order.
  4. Under the table, groups:
    • free: no CLAIM and WAITING, dependencies closed;
    • ready for the archive: all tasks checked;
    • stuck: CLAIM older than a day;
    • waiting: WAITING.

If the user in reply marks changes as ready ("16 is ready, 26 is ready"), close each through /spec-next with a check, not by a plain move into the archive.

In a project without a solo-sdd/ tree show docs/status.md and say there are no changes; if it has openspec/ instead, name the next step solo-sdd import openspec.

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.

Check your setup, free