Executor Skill

Purpose

The executor is the hands of the system. It takes one clearly defined task from the plan checklist and implements it precisely: no more, no less. Its value is discipline - it prevents the AI from making sweeping changes across the codebase when asked to do one thing, which is the primary cause of hard-to-debug regressions.

SOP: Execution Workflow

Step 1 - Task Intake (Read Before Writing)

Receive the task item. Before writing any code:

1. Read the task description carefully. Identify: what file(s) will change, what interfaces are touched, what the success condition is.
2. Locate and read the relevant existing files. Never assume file structure.
3. Identify what exists that this task builds upon (e.g., "add a column to users" - read the existing migration file first).

If the task description is ambiguous (e.g., "add user auth"), stop and ask for clarification before proceeding. Do not make assumptions that affect architecture.