# using-wrangler
> Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
- Author: Sam Hecht
- Repository: bacchus-labs/wrangler
- Version: 20260121161104
- Stars: 3
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/bacchus-labs/wrangler
- Web: https://mule.run/skillshub/@@bacchus-labs/wrangler~using-wrangler:20260121161104
---
---
name: using-wrangler
description: Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Skill tool before announcing usage, following brainstorming before coding, and creating TodoWrite todos for checklists
---
If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST read the skill.
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
# Getting Started with Skills
## Skill Usage Announcement
**MANDATORY**: When using this skill, announce it at the start with:
```
🔧 Using Skill: using-wrangler | [brief purpose based on context]
```
**Example:**
```
🔧 Using Skill: using-wrangler | [Provide context-specific example of what you're doing]
```
This creates an audit trail showing which skills were applied during the session.
## MANDATORY FIRST RESPONSE PROTOCOL
Before responding to ANY user message, you MUST complete this checklist:
1. ☐ List available skills in your mind
2. ☐ Ask yourself: "Does ANY skill match this request?"
3. ☐ If yes → Use the Skill tool to read and run the skill file
4. ☐ Follow the skill exactly
**Responding WITHOUT completing this checklist = automatic failure.**
**Note:** The Skill tool automatically announces skill loading. No separate announcement needed.
## Critical Rules
1. **Follow mandatory workflows.** Brainstorming before coding. Check for relevant skills before ANY task.
2. Execute skills with the Skill tool
## Common Rationalizations That Mean You're About To Fail
If you catch yourself thinking ANY of these thoughts, STOP. You are rationalizing. Check for and use the skill.
- "This is just a simple question" → WRONG. Questions are tasks. Check for skills.
- "I can check git/files quickly" → WRONG. Files don't have conversation context. Check for skills.
- "Let me gather information first" → WRONG. Skills tell you HOW to gather information. Check for skills.
- "This doesn't need a formal skill" → WRONG. If a skill exists for it, use it.
- "I remember this skill" → WRONG. Skills evolve. Run the current version.
- "This doesn't count as a task" → WRONG. If you're taking action, it's a task. Check for skills.
- "The skill is overkill for this" → WRONG. Skills exist because simple things become complex. Use it.
- "I'll just do this one thing first" → WRONG. Check for skills BEFORE doing anything.
**Why:** Skills document proven techniques that save time and prevent mistakes. Not using available skills means repeating solved problems and making known errors.
If a skill for your task exists, you must use it or you will fail at your task.
## Skills with Checklists
If a skill has a checklist, YOU MUST create TodoWrite todos for EACH item.
**Don't:**
- Work through checklist mentally
- Skip creating todos "to save time"
- Batch multiple items into one todo
- Mark complete without doing them
**Why:** Checklists without TodoWrite tracking = steps get skipped. Every time. The overhead of TodoWrite is tiny compared to the cost of missing steps.
## Announcing Skill Usage
When you use the Skill tool to load a skill, the system automatically announces:
```
The "{skill-name}" skill is loading
```
**This automatic announcement is sufficient.** You do NOT need to announce skill usage separately.
### If Using Skill Without Skill Tool
If you are following a skill's process without using the Skill tool (e.g., from memory or prior context):
You MUST announce with this simple format:
```
I'm using the [skill-name] skill to [brief description].
```
**Example:**
```
I'm using the brainstorming skill to refine your idea into a fully-formed design.
```
**Why announce when not using tool:**
- Confirms you're following a specific skill process
- Helps your human partner understand your approach
- Makes conversation history clear
**Why NOT announce when using tool:**
- Tool already announces skill loading
- Avoids redundant announcements
- Keeps conversation focused on work, not process overhead
# About these skills
**Many skills contain rigid rules (TDD, debugging, verification).** Follow them exactly. Don't adapt away the discipline.
**Some skills are flexible patterns (architecture, naming).** Adapt core principles to your context.
The skill itself tells you which type it is.
## Instructions ≠ Permission to Skip Workflows
Your human partner's specific instructions describe WHAT to do, not HOW.
"Add X", "Fix Y" = the goal, NOT permission to skip brainstorming, TDD, or RED-GREEN-REFACTOR.
**Red flags:** "Instruction was specific" • "Seems simple" • "Workflow is overkill"
**Why:** Specific instructions mean clear requirements, which is when workflows matter MOST. Skipping process on "simple" tasks is how simple tasks become complex problems.
## Summary
**Starting any task:**
1. If relevant skill exists → Use the Skill tool to load it
2. Follow what it says
**Skill has checklist?** TodoWrite for every item.
**Finding a relevant skill = mandatory to read and use it. Not optional.**