agentleFS
GCarin1GCarin1/Doctrina/.cursor/skills/doctrina-next/SKILL.md

doctrina-next

Skill1 starsChanged 3 days agoMITView on GitHub

Show and act on the next recommended Doctrina workflow step

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Run doctrina next and doctrina status to see open work and gate health.

    line 11
  2. Distinctive:

    Do the single highest-priority action it names (resume a change, apply a delta, archive, accept an ADR, fix index drift, …).

    line 12
  3. Distinctive:

    Use the read-only commands first.

    line 16

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/doctrina-next — next step for Doctrina

Decide the next step from the framework's own signals.

  1. Run doctrina next and doctrina status to see open work and gate health.
  2. Do the single highest-priority action it names (resume a change, apply a delta, archive, accept an ADR, fix index drift, …).
  3. Re-run doctrina next to confirm the item cleared.

Use the read-only commands first; never guess what is pending.

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.