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

@@ -63,7 +63,7 @@ Task tool (general-purpose):
**Dispatch code-reviewer subagent:**
```
Task tool (code-reviewer):
Use template at skills/collaboration/requesting-code-review/code-reviewer.md
Use template at requesting-code-review/code-reviewer.md
WHAT_WAS_IMPLEMENTED: [from subagent's report]
PLAN_OR_REQUIREMENTS: Task N from [plan-file]
@@ -103,7 +103,7 @@ After all tasks complete, dispatch final code-reviewer:
After final review passes:
- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
- Switch to skills/collaboration/finishing-a-development-branch
- **REQUIRED SUB-SKILL:** Use finishing-a-development-branch
- Follow that skill to verify tests, present options, execute choice
## Example Workflow
@@ -175,12 +175,15 @@ Done!
## Integration
**Pairs with:**
- skills/collaboration/writing-plans (creates the plan)
- skills/collaboration/requesting-code-review (review template)
- skills/testing/test-driven-development (subagents follow this)
**Required workflow skills:**
- **writing-plans** - REQUIRED: Creates the plan that this skill executes
- **requesting-code-review** - REQUIRED: Review after each task (see Step 3)
- **finishing-a-development-branch** - REQUIRED: Complete development after all tasks (see Step 7)
**Alternative to:**
- skills/collaboration/executing-plans (parallel session)
**Subagents must use:**
- **test-driven-development** - Subagents follow TDD for each task
See code-reviewer template: skills/collaboration/requesting-code-review/code-reviewer.md
**Alternative workflow:**
- **executing-plans** - Use for parallel session instead of same-session execution
See code-reviewer template: requesting-code-review/code-reviewer.md