agentleFS
Sign inStart free
jabrenajabrena/cursor-rules-java/skills/051-design-two-steps-methods/SKILL.md

051-design-two-steps-methods

Skill452 starsChanged 3 months agoApache-2.0View on GitHub

Use when a complex or risky code change should be split into Kent Beck's two-step method by first making the change easy through behavior-preserving preparatory refactoring, then making the intended behavior change once the design supports it. This should trigger for requests such as Apply two-step change; Make this risky change safer; Refactor before changing behavior; Separate preparation from behavior change. Part of Plinth Toolkit

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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. Distinctive:

    MUST: Keep Step 1 behavior-preserving.

    line 28
  2. Distinctive:

    MUST: Verify existing behavior after Step 1 using the project-appropriate tests, build, characterization tests, or manual checks

    line 29
  3. Distinctive:

    MUST: Verify the intended behavior after Step 2 with focused tests and relevant build checks

    line 31
  4. Very specific:

    Read references/051-design-two-steps-methods.md, inspect the relevant code and tests, and state the exact behavior or capability that must …

    line 46
  5. Distinctive:

    Run the relevant existing tests, build checks, characterization tests, or manual verification.

    line 58
  6. Distinctive:

    Verify the intended behavior with targeted tests and relevant project validation.

    line 66

≈ “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

Two-Step Change Method

Guide Java developers through complex or risky changes by keeping design preparation separate from behavior modification. This is an interactive SKILL.

What is covered in this Skill?

  • Clarifying the intended behavior change before editing
  • Identifying design obstacles that make the change difficult or risky
  • Step 1: behavior-preserving preparatory refactoring that makes the change easy
  • Validation that Step 1 preserves existing behavior
  • Step 2: the smallest intended behavior change after the design supports it
  • Verification that Step 2 delivers the intended behavior
  • Handoff to focused Java, framework, persistence, messaging, API, or testing skills while preserving the two-step sequence

Constraints

Separate behavior-preserving preparation from behavior-changing work, and validate after each step.

  • MUST: State the intended behavior change before proposing preparatory refactoring
  • MUST: Keep Step 1 behavior-preserving; do not mix broad refactoring with the intended behavior change
  • MUST: Verify existing behavior after Step 1 using the project-appropriate tests, build, characterization tests, or manual checks
  • MUST: Make Step 2 only after the design has been prepared and validated
  • MUST: Verify the intended behavior after Step 2 with focused tests and relevant build checks
  • MUST: Record assumptions and risks when preparation cannot be fully separated from behavior change

When to use this skill

  • Apply two-step change
  • Make this risky change safer
  • Refactor before changing behavior
  • Separate preparation from behavior change
  • Make the change easy, then make the easy change

Workflow

  1. Define the intended change

Read references/051-design-two-steps-methods.md, inspect the relevant code and tests, and state the exact behavior or capability that must change. Identify why the current design makes the change complex, risky, or hard to verify.

  1. Plan preparatory refactoring

Choose the smallest behavior-preserving refactoring that reduces the obstacle: extract method or class, clarify names, isolate dependencies, add seams for testing, move responsibilities, improve types, or add characterization tests before touching behavior.

  1. Make the change easy

Apply Step 1 as focused preparatory refactoring only. Keep commits, notes, or task boundaries clear enough that reviewers can see no intended behavior change is included.

  1. Validate preserved behavior

Run the relevant existing tests, build checks, characterization tests, or manual verification. If behavior changes unexpectedly, fix or revert the preparation before proceeding.

  1. Make the easy behavior change

Apply the smallest intended behavior change now that the design supports it. Use focused Java, framework, persistence, messaging, API, or testing skills when detailed implementation guidance is needed.

  1. Verify and report the outcome

Verify the intended behavior with targeted tests and relevant project validation. Report what was preparation, what changed behavior, what was verified after each step, and any remaining risks.

Reference

For detailed guidance, examples, and constraints, see references/051-design-two-steps-methods.md.

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