Best for
- Apply two-step change
- Make this risky change safer
- Refactor before changing behavior
Source profileQuality 83/100
jabrena/plinth/skills/051-design-two-steps-methods/SKILL.md
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 Toolkit
- Source repository stars
- 423
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-02
- Source checked
- 2026-08-04
Decision brief
What it does—and where it fits
Guide Java developers through complex or risky changes by keeping design preparation separate from behavior modification. This is an interactive SKILL.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/jabrena/plinth --skill "skills/051-design-two-steps-methods"Safe inspection promptEditorial
Inspect the Agent Skill "051-design-two-steps-methods" from https://github.com/jabrena/plinth/blob/fdaf68ccf0ffc4fb6147dc4ab805c34841ffaf33/skills/051-design-two-steps-methods/SKILL.md at commit fdaf68ccf0ffc4fb6147dc4ab805c34841ffaf33. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Workflow
1. Define the intended change
Define the intended changePlan preparatory refactoringMake the change easy - 02
Constraints
Separate behavior-preserving preparation from behavior-changing work, and validate after each step.
MUST: State the intended behavior change before proposing preparatory refactoringMUST: Keep Step 1 behavior-preserving; do not mix broad refactoring with the intended behavior changeMUST: Verify existing behavior after Step 1 using the project-appropriate tests, build, characterization tests, or manual checks - 03
When to use this skill
Apply two-step change
Apply two-step changeMake this risky change saferRefactor before changing behavior
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 83/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 423 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- jabrena/plinth
- Skill path
- skills/051-design-two-steps-methods/SKILL.md
- Commit
- fdaf68ccf0ffc4fb6147dc4ab805c34841ffaf33
- License
- Apache-2.0
- Collected
- 2026-08-04
- Default branch
- main
View the original 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Alternatives
Compare before choosing
Computed 9929,558
HKUDS/Vibe-Trading
strategy-generate
Create, modify, and optimize quantitative trading strategies, then backtest and evaluate them.
Computed 97106
AI-Unified-Process/marketplace
browserless-test
Creates Vaadin Browserless server-side unit tests for Vaadin views covering navigation, component interactions, form validation, grid operations, and notifications. Use when the user asks to "write Browserless tests", "write Vaadin UI unit tests", "unit test a Vaadin view without a browser", "create view tests with the official Vaadin testing framework", or mentions Browserless testing, SpringBrowserlessTest, browserless-test-junit6, UI Unit Testing, or server-side Vaadin testing.
Computed 9723
freenet/freenet-agent-skills
dapp-builder
Build and maintain decentralized applications on Freenet using river as a template. Guides through designing contracts (shared state), delegates (private state), and UI, and through upgrading a live dApp safely. Use when user wants to create a new Freenet dApp, design contract state, implement delegates, build a Freenet-connected UI, OR upgrade an existing dApp — bump freenet-stdlib, ship a new contract/delegate version (v2), fix a bug that re-keys the WASM, or migrate state across a contract/de
Computed 976
mgiovani/cc-arsenal
team-review
Multi-agent review team: architecture, security, performance, testing, style, docs/UX, plus an adversary that cross-examines the other 6, for security-sensitive, architectural, or large PRs (15+ files) where a single-agent pass risks missing cross-cutting issues. Use for auth/payments/PII changes, schema/pattern changes, compliance sign-off, or when asked to 'get the review team on this' / 'multi-agent review' / 'thorough review before merge'. For a standard PR or a quick pre-merge check, use /r