Clarify Requirements

Senior engineers read specifications differently than junior engineers. A junior reads what's there. A senior reads what's not there. They notice the missing error states, the unspecified edge cases, the assumptions that seem obvious today but will cause arguments next month.

This isn't pessimism — it's pattern recognition. After seeing enough features launch with gaps, you develop an instinct for the questions nobody thought to ask. This skill makes that instinct explicit and systematic.

Step 0: Load Existing Context

Before analyzing gaps in the requirements, understand what already exists. Building something that duplicates or conflicts with an existing capability is worse than missing an edge case.

If gjalla is available, query these tools first: