| name | meta-superpowers |
| description | Startup protocol for every task—discover applicable skills, run them, announce usage, and follow required workflows (brainstorming, TodoWrite checklists, etc.). |
If there is even a 1% chance a skill applies, you MUST read and use it. This is not optional.
Using Skills Effectively
Mandatory First-Response Protocol
Before responding to any user request:
- ☐ Mentally enumerate available skills.
- ☐ Ask: “Does ANY skill match this task?”
- ☐ If yes → Use the Skill tool to read/run it (do not rely on memory).
- ☐ Announce: “I’m using [Skill Name] to …”.
- ☐ Follow the skill exactly (brainstorming before coding, etc.).
Skipping this checklist is automatic failure.
Critical Rules
- Mandatory workflows – Brainstorming before coding, TDD, verification, etc. Instructions about WHAT to do never override HOW defined by skills.
- Execute via Skill tool – Always load the latest file; skills evolve.
Rationalization Triggers (STOP immediately)
- “This is simple”
- “I’ll just gather info first”
- “I remember the skill”
- “Skill is overkill”
- “Let me do one thing before checking”
These are warning signs that you’re about to skip process. Don’t.
Skills with Checklists
If a skill has a checklist, create TodoWrite items for each step. No mental tracking, no batching, no skipping. Mark complete only when done.
Announcing Skill Usage
Always tell your partner: “I’m using [Skill] to [task].”
- Promotes transparency and ensures accountability.
- Confirms you actually read the skill.
Instructions vs. Workflows
User instructions describe outcomes, not process. You still must execute brainstorming, TDD, verification, etc., unless explicitly told otherwise.
Summary
- Check for relevant skills before doing anything.
- Use the Skill tool, announce usage, follow instructions exactly.
- Convert skill checklists into TodoWrite tasks.
Failing to use applicable skills = failing the task.
