Improve skill cross-references for clarity and compliance

Update all skill references to use explicit requirement markers:
- REQUIRED BACKGROUND: For prerequisite understanding
- REQUIRED SUB-SKILL: For mandatory workflow dependencies
- Complementary skills: For optional but helpful related skills

Changes:
- Remove old path format (skills/collaboration/X → X)
- Add explicit "REQUIRED" markers to make dependencies clear
- Update Integration sections with categorized skill relationships
- Fix non-existent skill references
- Update cross-reference documentation in writing-skills

This makes it immediately clear which skills MUST be used vs optional references,
helping Claude understand and comply with skill dependencies.
This commit is contained in:
Jesse Vincent
2025-10-17 10:18:50 -07:00
parent 9e82a51f34
commit 141953a4be
11 changed files with 49 additions and 42 deletions

View File

@@ -111,7 +111,7 @@ You MUST complete each phase before proceeding to the next.
**WHEN error is deep in call stack:**
See skills/root-cause-tracing for backward tracing technique
**REQUIRED SUB-SKILL:** Use root-cause-tracing for backward tracing technique
**Quick version:**
- Where does bad value originate?
@@ -176,7 +176,7 @@ You MUST complete each phase before proceeding to the next.
- Automated test if possible
- One-off test script if no framework
- MUST have before fixing
- See skills/testing/test-driven-development for writing proper failing tests
- **REQUIRED SUB-SKILL:** Use test-driven-development for writing proper failing tests
2. **Implement Single Fix**
- Address the root cause identified
@@ -277,11 +277,14 @@ If systematic investigation reveals issue is truly environmental, timing-depende
## Integration with Other Skills
This skill works with:
- skills/root-cause-tracing - How to trace back through call stack
- skills/defense-in-depth - Add validation after finding root cause
- skills/testing/condition-based-waiting - Replace timeouts identified in Phase 2
- skills/verification-before-completion - Verify fix worked before claiming success
**This skill requires using:**
- **root-cause-tracing** - REQUIRED when error is deep in call stack (see Phase 1, Step 5)
- **test-driven-development** - REQUIRED for creating failing test case (see Phase 4, Step 1)
**Complementary skills:**
- **defense-in-depth** - Add validation at multiple layers after finding root cause
- **condition-based-waiting** - Replace arbitrary timeouts identified in Phase 2
- **verification-before-completion** - Verify fix worked before claiming success
## Real-World Impact