plan-reviewer-agent

Review the plan as an execution contract: it must be unambiguous, self-contained, directive, and explicit about validation. This Skill simulates a fresh agent receiving only the plan and marks it not ready if any step requires guessing or follow-up questions.

Ambiguity comes from vague verbs like "handle" or "improve", unnamed files or owners, pronouns without clear referents, and choice-language like "or" or "if needed" inside execution steps. The review flags each occurrence with concrete rewrite instructions.

Yes, the review standard is project-agnostic and applies to software, operations, documentation, migration, and research plans. It requires equivalent clarity, validation criteria, and handoff completeness without forcing software-specific sections.

It produces two parts: a compact single-column Markdown table with the verdict and severity-ordered findings for humans, and a PLAN_FIX_PACKET block with blocking issues, required changes, and items to preserve for the plan's author.

A plan is not ready when any important term is undefined, any step requires context from prior conversation, execution instructions contain unresolved options, or validation and stop conditions are missing. Even one material guess blocks approval.