Fix terminology in multiple practices

output_skills/practices/complexity-review/SKILL.md

@@ -80,7 +80,7 @@ Use these categories to systematically challenge technical proposals. For the co
 **Do NOT use when:**
 - Simple feature implementation (use hamburger-method or story-splitting instead)
 - Work is already planned and simple
-- User asks "how to" implement something specific (use micro-steps-coach instead)
+- User asks "how to" implement something specific (use small-safe-steps instead)
 
 ---
 
@@ -361,7 +361,7 @@ This skill works in sequence with other skills:
 **Typical workflow:**
 1. **story-splitting** or **hamburger-method**: Break down features into small slices
 2. **complexity-review** (THIS SKILL): Review proposed technical approach, simplify
-3. **micro-steps-coach**: Break simplified approach into 1-3h steps
+3. **small-safe-steps**: Break simplified approach into 1-3h steps
 
 **Use this skill when:**
 - User proposes a specific technical solution (after understanding what they want to achieve)
@@ -370,7 +370,7 @@ This skill works in sequence with other skills:
 
 **Do NOT use this skill when:**
 - The approach is already simple (single database, monolith, basic API)
-- User is asking "how to implement" (that's micro-steps-coach territory)
+- User is asking "how to implement" (that's small-safe-steps territory)
 
 ---
 

output_skills/practices/hamburger-method/REFERENCE.md

@@ -599,9 +599,9 @@ Use these quality gradients to generate 4-5 options per layer systematically.
 - Use complexity-review to challenge high-complexity options
 - Result: Ensure simplest options are truly simple
 
-**Combine with micro-steps-coach:**
+**Combine with small-safe-steps:**
 - Use hamburger method to choose vertical slice
-- Use micro-steps-coach to break the slice into 1-3h steps
+- Use small-safe-steps to break the slice into 1-3h steps
 - Result: Clear path from feature → slice → implementation steps
 
 ---

output_skills/practices/hamburger-method/SKILL.md

@@ -22,7 +22,7 @@ Expert in applying the Hamburger Method (by Gojko Adzic) to break down large fea
 
 **Do NOT use when:**
 - Story has obvious "and", "or", "manage" indicators (use story-splitting instead)
-- User is asking HOW to implement (use micro-steps-coach instead)
+- User is asking HOW to implement (use small-safe-steps instead)
 - Feature is already small (< 1 day work)
 
 ---
@@ -222,7 +222,7 @@ This skill works in sequence with other skills:
 1. **story-splitting**: Detect and split oversized stories with obvious red flags
 2. **hamburger-method** (THIS SKILL): For stories that are large but not obviously splittable, generate layers + options
 3. **complexity-review**: Review proposed vertical slice, simplify if needed
-4. **micro-steps-coach**: Break chosen vertical slice into 1-3h implementation steps
+4. **small-safe-steps**: Break chosen vertical slice into 1-3h implementation steps
 
 **Use this skill when:**
 - Feature is large but doesn't have obvious "and", "or", "manage" indicators
@@ -238,7 +238,7 @@ This skill works in sequence with other skills:
 - User: "Implement user notifications" (no obvious split points)
 - Apply hamburger-method → Identify 5 layers, generate options, compose smallest slice
 - Then use complexity-review → Ensure simplest slice is truly simple
-- Then use micro-steps-coach → Break slice into 1-3h steps
+- Then use small-safe-steps → Break slice into 1-3h steps
 
 ---
 

output_skills/practices/small-safe-steps/SKILL.md

@@ -292,17 +292,17 @@ This skill works in sequence with other skills:
 1. **story-splitting**: Break down large user stories into smaller ones
 2. **hamburger-method**: Choose vertical slice to implement first
 3. **complexity-review**: Review and simplify technical approach
-4. **micro-steps-coach** (THIS SKILL): Break simplified approach into 1-3h steps
+4. **small-safe-steps** (THIS SKILL): Break simplified approach into 1-3h steps
 
 **Use this skill when:**
 - User knows WHAT to build and asks HOW to implement it
 - After architectural decisions are made (complexity-review)
 - When planning execution of a story/feature/refactoring
 
 **Integration examples:**
-- Use **story-splitting** first → "Admin can create user" → Then use micro-steps-coach to plan the 1-3h steps
-- Use **hamburger-method** first → Choose slice (manual email notification) → Then use micro-steps-coach for implementation steps
-- Use **complexity-review** first → Simplify to PostgreSQL instead of Kafka → Then use micro-steps-coach for migration steps
+- Use **story-splitting** first → "Admin can create user" → Then use small-safe-steps to plan the 1-3h steps
+- Use **hamburger-method** first → Choose slice (manual email notification) → Then use small-safe-steps for implementation steps
+- Use **complexity-review** first → Simplify to PostgreSQL instead of Kafka → Then use small-safe-steps for migration steps
 
 **Do NOT use this skill when:**
 - User hasn't decided what to build yet (use story-splitting first)

output_skills/practices/story-splitting/SKILL.md

@@ -23,7 +23,7 @@ Expert at detecting when work is too big and applying proven splitting heuristic
 **Do NOT use when:**
 - Story is already small and focused (< 1 day work)
 - Feature needs layered analysis without obvious split points (use hamburger-method instead)
-- User asks HOW to implement (use micro-steps-coach instead)
+- User asks HOW to implement (use small-safe-steps - instead)
 
 ---
 
@@ -372,7 +372,7 @@ This skill works in sequence with other skills:
 1. **story-splitting** (THIS SKILL): Detect linguistic red flags, split stories into smaller ones
 2. **hamburger-method**: For stories still large after splitting, apply layered analysis
 3. **complexity-review**: Review technical approach for each small story
-4. **micro-steps-coach**: Break each story into 1-3h implementation steps
+4. **small-safe-steps**: Break each story into 1-3h implementation steps
 
 **Use this skill when:**
 - Story contains obvious red flags ("manage", "and", "or", "including")
@@ -388,7 +388,7 @@ This skill works in sequence with other skills:
 - Original: "Admin can manage users and roles"
 - Apply story-splitting → Split into: (1) "Create user", (2) "Edit user", (3) "Assign role"
 - Story #1 still feels large → Apply hamburger-method to identify layers + options
-- Choose simplest vertical slice → Apply micro-steps-coach to plan 1-3h steps
+- Choose simplest vertical slice → Apply small-safe-steps to plan 1-3h steps
 
 ---