example-skill

name	example-skill
description	A reusable workflow template. Customize phases for your use case.
allowed-tools	["Read","Write","Bash","Edit","Grep","Glob"]
routing	{"triggers":["example workflow","run example"],"force_route":false}

Example Skill

A structured workflow for [YOUR USE CASE]. This skill guides Claude through a repeatable process with clear phases and gates.

When to Use

• When you need to [accomplish X]
• When the task involves [Y steps]
• Triggered by: "example workflow", "run example"

Phases

Phase 1: UNDERSTAND

Goal: Gather context before acting.

1. Read relevant files
2. Identify constraints
3. List what success looks like

Gate: Can you describe the end state in one sentence? If not, keep gathering context.

---

Phase 2: PLAN

Goal: Design the approach.

1. List the changes needed
2. Identify risks or dependencies
3. Choose the simplest path that works

Gate: Plan is concrete enough to execute without further questions.

---

Phase 3: EXECUTE

Goal: Make the changes.

1. Implement the plan
2. Keep changes minimal and focused
3. Commit logical chunks (not one giant change)

Gate: All planned changes are complete.

---

Phase 4: VERIFY

Goal: Prove it works.

1. Run tests (if they exist)
2. Check the output matches expectations
3. Verify no regressions

Gate: Evidence exists that the change works correctly.

---

Reference Files

For deeper patterns and examples, see:

• references/patterns.md — Detailed reference material

Anti-Patterns

Don't Do This	Do This Instead
Skip verification	Always prove it works
Change too many things at once	One logical change per commit
Assume it works because it looks right	Run it and check output