agentleFS
dccooperdccooper/agentic-psychologist/.agents/skills/next-step/SKILL.md

next-step

Skill2 starsChanged 15 days agoMITView on GitHub

Continue to the next step of the current lesson. Use when the learner types /next-step or says they're ready to continue.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use simplify, interview and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Hugging FaceSkill

    simplify

    Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.

    Also in 3 projects that use this

  • dazuckSkill

    interview

    Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    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:

    Read workspace/progress.md to find the current lesson and the last completed checkpoint.

    line 8
  2. Distinctive:

    If the current checkpoint isn't confirmed yet, check it first (look at the file, or ask the learner what they see).

    line 10
  3. Distinctive:

    When a lesson's final checkpoint is confirmed:

    line 12
  4. Very specific:

    Update workspace/progress.md only at a pause point or the end of a lesson (see AGENTS.md), not after every step.

    line 16

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

Next step

  1. Read workspace/progress.md to find the current lesson and the last completed checkpoint.
  2. Open that lesson's script in lessons/.
  3. If the current checkpoint isn't confirmed yet, check it first (look at the file, or ask the learner what they see). If the checkpoint is about a file's contents, read the file and compare. Don't answer from memory. Don't skip ahead.
  4. Give the learner the next single step, with a one-line "why."
  5. When a lesson's final checkpoint is confirmed:
    • Mark the lesson complete in progress.md.
    • Give a two-sentence recap of what they can now do.
    • Set the next lesson (follow the order in lessons/README.md). If the next lesson has no script file in lessons/ yet, skip to the next one that does, and tell the learner in one sentence that the skipped lessons are still being written. If an earlier lesson now has a script but isn't marked complete, offer it first (see /start-course, catch-up check). Before the first Module 3 lesson, ask which path they want, Clinic (3A) or Lab (3B), with one line on each, and record their choice.
  6. Update workspace/progress.md only at a pause point or the end of a lesson (see AGENTS.md), not after every step. Everything you need for the update is in progress.md and the lesson script. Don't search anywhere else.

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.