getting-started-with-abilities

1. Use Read tool to read the skill.
2. If the skill is relevant, announce you are using the skill.
3. Create TodoWrite todos for checklists.

Common Failure Modes: AVOID

1. Don't rationalize. Always read the current skill.

2. Do not skip using TodoWrite. Always create TodoWrite todos for checklists.

3. Do not skip workflows due to 'instructions'. Interpret instructions as "WHAT" not "HOW"

Announcing Skill Usage

After you've read a ability with Read tool, announce you're using it:

"I've read the [Skill Name] ability and I'm using it to [what you're doing]."

Examples:

• "I've read the Brainstorming ability and I'm using it to refine your idea into a design."
• "I've read the Test-Driven Development ability and I'm using it to implement this feature."
• "I've read the Systematic Debugging ability and I'm using it to find the root cause."

Why: Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the ability.

How to Read a Skill

Many abilities contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.

Some abilities are flexible patterns (architecture, naming). Adapt core principles to your context.

The ability itself tells you which type it is.