clarify

Run the clarify skill on your ticket or design brief. It parses each acceptance criterion, checks current system behavior in the code, and asks you only the business questions the ticket left unanswered, producing a Clarification Brief for the plan phase.

A Clarification Brief is a markdown artifact containing per-AC resolutions, seam-gap decisions, confirmed constraints, and deferred questions. It contains only business language with no file paths or implementation details, and is consumed directly by the planning step.

Use clarify when acceptance criteria contain unknowns, silent edge cases, or conflicts with existing system behavior. If requirements are already unambiguous, you can skip it since the plan phase accepts assumptions that clarify would otherwise resolve.

No. Clarify reads code only as evidence of current business behavior and never proposes implementation changes. Implementation mapping, owner identification, and change specification are explicitly delegated to the plan phase.

You can defer the question to a stakeholder, which is logged in the brief's Deferred Questions table, or mark the item as needing a spike. The brief records a NEEDS_STAKEHOLDER or NEEDS_SPIKE status instead of blocking entirely.