agentleFS
kidowkidow/skills/step-by-step/SKILL.md

step-by-step

Skill2 starsChanged 6 months agoMITView on GitHub

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree, and drawing HTML visual references when a question is easier answered visually. Use when user wants to stress-test a plan, get grilled on their design, or mentions "step by step".

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

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

  • 0

    Common

    Most of the 4 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. Distinctive:

    Ask the questions one at a time.

    line 8
  2. Distinctive:

    If a question can be answered by exploring the codebase, explore the codebase instead.

    line 10
  3. Very specific:

    If a question needs a UI reference — layout, spacing, hierarchy, flow, or design direction — use the visualstorming skill to draw an HTML …

    line 12
  4. Very specific:

    If the visualstorming skill is not installed, ask the user once whether to install it (npx skills@latest add kidow/skills/visualstorming).

    line 14

“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

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time.

If a question can be answered by exploring the codebase, explore the codebase instead.

If a question needs a UI reference — layout, spacing, hierarchy, flow, or design direction — use the visualstorming skill to draw an HTML reference instead of asking in text.

If the visualstorming skill is not installed, ask the user once whether to install it (npx skills@latest add kidow/skills/visualstorming). If they decline, draw the HTML reference yourself using your own judgment.

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.