Fresh review

Judge the artifact against the requested outcome and available evidence. Follow project expectations and scale the review to the work. This skill does not require a branch, plan file, or another installed skill.

Establish the target

Identify the artifact, intent, applicable constraints, and the questions that matter. Use a stable copy, version, or snapshot when possible. If work changes during review, state what version was reviewed and revisit affected findings.

For code, inspect the relevant change and surrounding behavior using the available comparison tools. For writing, research, or plans, check the argument, evidence, audience, omissions, and internal consistency.

Choose the review context

• Use a separate reviewer when supported, permitted, and useful. Give it the artifact and intent without steering it toward your expected findings.
• For independent review, choose a reviewer that did not author the artifact and minimize inherited implementation discussion. Disclose limits when the environment cannot separate that context.
• Choose review lenses based on the actual risks. One focused reviewer may suffice; add a security or other specialist perspective when justified.
• A permitted subprocess worker is an option only when suitable tooling and lifecycle controls are available. Never use it to bypass a restriction on delegation.
• Without a separate context, deliberately re-examine the artifact yourself. Label this self-review and acknowledge its limits.
• If independent review is explicitly required and cannot be obtained, provide a handoff brief and state that the independent review remains outstanding. Do not substitute self-review while claiming that requirement is complete.