agentleFS
walutani1walutani1/gtm-groundwork/.claude/skills/next/SKILL.md

next

Skill0 starsChanged 3 months agoMITView on GitHub

Where are we and what's next - reads the project's stage and offers to run the next pipeline step. Use anytime the user asks "where were we", "what's next", "continue", or invokes /next.

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use quick, project and 10 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.
  • codebycoreySkill

    quick

    Quick start a change with minimal interaction. Use when fast-tracking a straightforward change that needs proposal, design, and tasks in one step.

    Also in 3 projects that use this

  • BugRogerSkill

    project

    Project lifecycle management. Dispatches to Ada.

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 9 projects that use this

  • MicrosoftSkill

    cleanup

    Also in 4 projects that use this

  • ArvorCoSkill

    clarify

    Identify and resolve ambiguities in feature specifications. Use when spec has unclear requirements. Triggers on: clarify spec, resolve ambiguities, clarify requirements.

    Also in 3 projects that use this

  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 3 projects that use this

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 39 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:

    Read the Stage line in prd.md and the checkboxes in tasks.md.

    line 10

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

Orient, then offer. Never make the user remember the pipeline.

  1. Read the Stage line in prd.md and the checkboxes in tasks.md.
  2. Tell the user in 2-3 plain sentences: what stage the project is at, what was last completed, and what the next step is.
  3. Offer to run the next step now (one question, default yes).

Stage -> next step

Stage in prd.mdNext
not-started (or template placeholders)/kickoff
kickoff-done/refine-prd
prd-locked/mockup
mockup-approvedBuild loop: next unchecked feature in tasks.md (checklist step 4)
buildingContinue the build loop; if all features checked, pre-deploy checks (step 5)
predeploy-passedDeploy (checklist step 6)
deployedNothing pending - offer improvements or close out

Rule for every agent: when you COMPLETE a stage, update the Stage line in prd.md and end your message by offering the next step by name.

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.