Find agent skills by outcome

Risks: What could break

what needs monitoring

Keep it scannable—bullet points

no fluff. Transparency about tradeoffs.

How: Key implementation decisions (patterns used

structure chosen)

Smells: Tech debt

workarounds

- Once action taken

it cannot be undone

Education

**Comments Explain WHY

Not WHAT:**

- Give concrete facts

not abstract comparisons

- Share recommendation with reasoning

then ask user to decide

- When multiple valid approaches: speculate

think aloud

- For each option: WHY it exists

HOW it works

- On transient errors

retry (unless explicit limit reached)

Business

- On other errors

change strategy—don't repeat failed approaches

- If hypotheses disproven

generate new ones from gathered information

- Policies

rules

- Policy rules

mandatory prerequisites

Productivity

- For exploratory tasks

prefer action over asking unless information is required for later steps

Productivity

- Each task completable in a scoped

small change

2. Apply Deepthink Protocol (reason about dependencies

risks

If you can track internally

do it internally.

If not

create `todos.txt` at project root—update as you go

- Scan package.json

Cargo.toml

- Identify gaps

ambiguities

- Check for .claude/ folder (agents

commands

Before any action

gather context and enhance the request internally: