agentsclimarketplace
Sign in

051 design two steps methods

Skill jabrena/plinth/skills/051-design-two-steps-methods

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 ToolkitFrom its SKILL.md

Install
npx -y skills add jabrena/plinth --skill 051-design-two-steps-methods

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.8 KB, as published. Nobody here has run it

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.

What ships with it: 1 file

6.3 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most design frontend skills give

Counted across 1,179 of the 2,086 authors here whose files we hold, read 2026-09-06

  • Commit to a bold aesthetic directionin 31 of 1179, across 24 files
  • Prefer component composition over inheritancein 28 of 1179, across 14 files
  • Animate only transform and opacity propertiesin 27 of 1179, across 22 files
  • Memoize expensive computations with useMemoin 26 of 1179, across 13 files
  • Use semantic HTML elementsin 24 of 1179, across 23 files
  • Virtualize long lists for performancein 21 of 1179, across 10 files
  • Use CSS variables for design tokensin 20 of 1179, across 14 files
  • Implement loading, empty, and error statesin 20 of 1179
  • Lazy load heavy components with Suspensein 19 of 1179, across 8 files
  • Respect prefers-reduced-motion media queriesin 18 of 1179, across 10 files
  • Prioritize CSS-only animations for HTMLin 18 of 1179, across 16 files
  • Use compound components for related UI elementsin 18 of 1179, across 7 files

Said here and by no other author read

  • State the intended behavior change first
  • Perform preparatory refactoring to make changes easy
  • Keep step one behavior-preserving
  • Verify existing behavior after step one
  • Record assumptions if preparation cannot be separated

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,194. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.