agentleFS
Sign inStart free
librosdeialibrosdeia/builder-method-claude-plugin/skills/next/SKILL.md

next

Skill0 starsChanged 5 days agoMITView on GitHub

Continue a Builder Method project — shows where the project is, what is done and missing, and continues with the next step. Use when the user asks "what's next", "continue", "let's keep going" or comes back to a project that has a builder/ folder.

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 8 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

  • 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

  • GoogleSkill

    critique

    Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If builder/state.json is missing or damaged, follow "Damaged or missing state" in state-rules.md.

    line 15
  2. Very specific:

    If there is nothing at all, offer to start a project with /builder:start, and stop.

    line 16
  3. Very specific:

    If the phase is in Build › build: the first task of the current cycle that isn't done, in plan order.

    line 26
  4. Very specific:

    If the current phase is complete: the next phase, skipping not_applicable phases.

    line 27
  5. Distinctive:

    If there is debt, mention it in one line, and offer to review it first.

    line 28
  6. Distinctive:

    Ask "Shall we continue?" (or the equivalent in the user's language).

    line 34

“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

What's next

Read and follow:

  • ${CLAUDE_PLUGIN_ROOT}/skills/_shared/tone.md
  • ${CLAUDE_PLUGIN_ROOT}/skills/_shared/state-rules.md
  • ${CLAUDE_PLUGIN_ROOT}/skills/_shared/gates.md

1. Read the state

  • If builder/state.json is missing or damaged, follow "Damaged or missing state" in state-rules.md.
  • If there is nothing at all, offer to start a project with /builder:start, and stop.

2. Show the summary

Print the progress summary exactly as the status skill defines it (${CLAUDE_PLUGIN_ROOT}/skills/status/SKILL.md, section "Summary format").

3. Decide the next step

Work it out in this order:

  1. The current phase's first step that isn't done or skipped.
  2. If the phase is in Build › build: the first task of the current cycle that isn't done, in plan order. Name it with its id and title (e.g. "T6 — Cancel button").
  3. If the current phase is complete: the next phase, skipping not_applicable phases. Mention any "warns also if" conditions from gates.md for it.
  4. If there is debt, mention it in one line, and offer to review it first.

Say the next step in one sentence, with the command that runs it (/builder:<phase>).

4. Continue

Ask "Shall we continue?" (or the equivalent in the user's language). When they confirm, follow that phase's skill from the step you named. If the user said to only tell them the next step, stop after naming it.

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