Mandatory Skill Selection

ALWAYS review available skills BEFORE starting work.

Process

1. Check <available_skills> in system prompt
2. Read skill descriptions - they tell you when to use them
3. Match descriptions to current task
4. Select ALL applicable skills
5. Announce selection to user

Skill Categories

Mental checklist for skill selection:

• Core Philosophy - Code quality, honesty, evidence-based claims?
• Design Principles - Architecture, modularity, coupling, simplicity?
• Testing & Quality - TDD, code review, verification?
• Process & Recovery - Debugging strategies, baseline restoration?
• Code Improvement - Refactoring, incremental improvements?
• Technology-Specific - Framework/language patterns (Buki skills)?

Communication

At task start:

"Using these skills:
- skill-name (reason it applies)"

During work (if new skills identified):

"Identified additional skill needed:
- skill-name (reason)"

Key Points

• Skill descriptions are source of truth
• Multiple skills often apply to one task
• Quality/verification skills apply to most tasks
• Announce skills BEFORE coding, not after

Review skills FIRST, not after work starts.