# Skill Procedure in Full

Use this procedure when a specialized skill/workflow is available and the task
explicitly names it or clearly matches its stated purpose.

## Selection

1. Identify whether a named skill applies.
2. If not named, determine whether the task clearly falls into a skill's
   declared domain.
3. Select the minimum set that covers the task.
4. State in a working update which procedure is being used and why.

Do not carry a skill automatically into unrelated future work merely because it
was useful once.

## Read-before-act rule

Before taking task actions under a selected skill:

1. read the skill instructions completely;
2. resolve and read required referenced instructions/resources;
3. use the same provider/access mechanism requested by the skill;
4. prefer supplied scripts/templates/assets over retyping their behavior;
5. preserve user instructions when they conflict with a skill's defaults.

Do not delegate the interpretation of a selected skill's instructions to
another agent. A worker may do task work after the parent has applied the
procedure.

## Discovery rule

When a relevant specialization is not already available, search the configured
skill/index surface using a task-specific phrase. Inspect the candidate
instructions before using it. Do not invent a skill name or claim a capability
exists without checking.

## Failure rule

If a requested skill cannot be read or applied:

1. state the precise issue briefly;
2. choose the best safe fallback process;
3. continue within the user’s scope when possible.

## Context rule

Skill instructions are procedure, not task evidence. Load only the selected
skill and required references. Do not flood a task request with unrelated
framework catalog material.

## Delivery rule

If the skill materially affected design or implementation, mention that in the
handoff. Do not mention a skill that was merely inspected and did not affect
the work.