Standardize skill frontmatter names to lowercase and kebab-case

- Update all 20 skill frontmatter names to match their directory names in lowercase
- Fix defense-in-depth name (was Defense-in-Depth-Validation)
- Fix receiving-code-review name (was Code-Review-Reception)
- Update all skill announcements and cross-references to use lowercase names
- Update commands redirects to reference lowercase skill names

Ensures consistent naming: skill directory names, frontmatter names, and documentation
references all use lowercase kebab-case format (e.g., brainstorming, test-driven-development)
This commit is contained in:
Jesse Vincent
2025-10-17 09:40:36 -07:00
parent 2076e49d18
commit 48410c7f19
22 changed files with 33 additions and 33 deletions

View File

@@ -1,5 +1,5 @@
---
name: Executing-Plans
name: executing-plans
description: Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
---
@@ -11,7 +11,7 @@ Load plan, review critically, execute tasks in batches, report for review betwee
**Core principle:** Batch execution with checkpoints for architect review.
**Announce at start:** "I'm using the Executing Plans skill to implement this plan."
**Announce at start:** "I'm using the executing-plans skill to implement this plan."
## The Process
@@ -45,7 +45,7 @@ Based on feedback:
### Step 5: Complete Development
After all tasks complete and verified:
- Announce: "I'm using the Finishing a Development Branch skill to complete this work."
- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
- Switch to skills/collaboration/finishing-a-development-branch
- Follow that skill to verify tests, present options, execute choice