Clarify

Use this skill to move a target from fuzzy or error-prone toward implementation-ready clarity. The target may be a repository, uncommitted diff, plan, beads/work items, or a mix of plan plus code.

The workflow is intentionally chained. Each pass should feed the next pass with concrete findings, not restart from taste or vague preference.

Operating Rules

• Start by identifying the target: codebase, uncommitted diff, recent changes, plan, beads/work items, or mixed target. Ask one blocking question only if the target is genuinely unclear.
• Prefer evidence from files, diffs, tests, docs, work items, and execution traces over style opinions.
• Preserve already-firm specifications. Change only the parts that are wrong, ambiguous, duplicated, shallow, or misleading.
• Make small granular edits when editing shared artifacts. Assume other agents may be working in the same tree.
• Do not create churn. Repeated runs should converge: update existing findings, ledgers, issues, or plan text instead of duplicating them.
• If changing code, preserve behavior unless the review finds a real bug. Add or update focused tests when the risk justifies it.
• When producing issues, include title, problem, suggested remediation, and acceptance criteria.

Chain Overview

Run the passes in this order unless the user asks for a narrower mode: