Lean and dense with no explaining of concepts Claude already knows; every section (When to Use, Operation settings, How It Works, Example) earns its place; not a 2 because there is no unnecessary padding to tighten.

Gives concrete directives (phase mask sequence, named gates, first-move rule, when to add security-reviewer) and a concrete example, but execution is externalized to the referenced orch-pipeline engine rather than being copy-paste executable on its own; not a 3 because it is not fully self-contained/executable, not a 1 because guidance is specific rather than vague.

Clear sequence (phase mask 0→…→6, numbered How It Works) with explicit validation checkpoints (Gate 1 plan/changed-test approval, Gate 2 pre-commit, shown as [GATE 2: confirm] in the example); not a 2 because checkpoints are explicit rather than implicit or missing.

Under-50-line body with well-organized sections and one clearly-signaled one-level reference (../orch-pipeline/SKILL.md); per the guideline, simple skills with no needed external references can score 3 on well-organized sections alone.

Lists multiple concrete actions — "update its tests to the new spec, change the implementation to match, review, and gated commit" — matching the anchor for several specific concrete actions; not a 2 because it goes beyond naming a domain plus a few actions.

Explicitly answers both what (the four named actions) and when ("Use when behavior is not broken but should be different"); not a 2 because the trigger is explicit rather than merely implied.

Contains relevant terms ("altering...feature", "should be different") but omits the natural phrasings users actually say ("change", "adjust", "instead of X do Y"), which appear only in the body; not a 3 because coverage of common variations is thin, not a 1 because some relevant keywords are present.

"behavior is not broken but should be different" carves a clear niche distinct from fixing broken features and adding new ones, making conflict with sibling skills unlikely.