agentleFS
Sign inStart free
davidondrejdavidondrej/skills/skills/thinking-and-docs/4x4/SKILL.md

4x4

Skill4.2k starsChanged 8 days agoMITView on GitHub

Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Load context fast: Use what's already in the thread.

    line 21
  2. Distinctive:

    Pick the order: Start with the set whose answers most change the others.

    line 22
  3. Distinctive:

    Show one set at a time: Never preview or list the other sets.

    line 24
  4. Distinctive:

    Present the plan: After set 4, give plain step-by-step instructions to execute the work properly, built from the user's answers.

    line 26
  5. Distinctive:

    No meta questions, like how to measure success or what to test first.

    line 48
  6. Distinctive:

    If the user calls a question bad, replace it or drop it.

    line 50
  7. Distinctive:

    If an answer contradicts an ADR or scope, point it out in the plan.

    line 51
  8. Distinctive:

    If an answer opens a big new question, note it in the plan.

    line 52

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

4x4

Get the user's judgment, taste, and decisions in 4 quick rounds. 16 open questions. A full run should take them 2–3 minutes.

The 4 sets

These are defaults. Adapt their names and focus to pull the most judgment and taste out of the user for this topic.

  1. Product — what it does, who it's for, UI/UX, scope.
  2. Software design — architecture, data, boundaries, what to reuse or delete.
  3. Practical — execution order, rollout, what ships first.
  4. Edge cases — the 4 most likely ways this breaks or surprises users. Each question asks how to handle one.

Workflow

  1. Load context fast. Use what's already in the thread. Skim only the files and docs that matter (scopes, ADRs, the diff). No research, no subagents.
  2. Pick the order. Start with the set whose answers most change the others.
  3. Pick 4 questions per set. Choose the 4 decisions with the biggest impact that only the user can make. Never ask what the code, docs, or common sense already answer. Skip anything already decided.
  4. Show one set at a time. Never preview or list the other sets. Stop and wait. Show the next set only after the user answers.
  5. Adapt. Rewrite later sets based on earlier answers.
  6. Present the plan. After set 4, give plain step-by-step instructions to execute the work properly, built from the user's answers. Chat only. Then stop. Don't build or write docs until the user says go.

Message format

## Set 2/4 · Software design

1. Where should X live?

2. ...

3. ...

4. ...

Nothing else. No intro, no outro.

Rules

  • Open questions only. Never give options, picks, recommendations, or hints. The point is the user's own thinking.
  • One short sentence per question. Concrete, plain English, clear on first read.
  • No meta questions, like how to measure success or what to test first. Ask about the work itself.
  • Vague or skipped answer: move on and use your judgment.
  • If the user calls a question bad, replace it or drop it. Your call.
  • If an answer contradicts an ADR or scope, point it out in the plan.
  • If an answer opens a big new question, note it in the plan. Don't add a 5th question.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about davidondrej/skills

The biggest 5 of 29 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 29

Talked about on GitHub (29 times).

On GitHub · 29

24 more on GitHub

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