evaluate-issue-plan

To verify an implementation plan against your codebase, you can evaluate the posted plan comments for factual accuracy by checking referenced paths and described behaviors against repository code and issue requirements. This process confirms spec compliance and implementability.

Checking spec compliance and implementability involves a two-phase evaluation ensuring the plan satisfies issue requirements without adding scope, and confirming an executor could implement it without guessing. This verifies factual claims against existing repository paths and behaviors.

Detecting file overlap conflicts requires checking the implementation plan's referenced paths against open pull request files. This read-only repo context check identifies potential conflict risks before execution begins, preventing unimplementable work.

Yes, you can apply automated label management after evaluating an implementation plan. Following a structured plan evaluation comment, the workflow updates GitHub issue labels to indicate the verified status and readiness for action.

Enforcing trust-based selection involves applying trust-gated logic to only process implementation plan comments authored by trusted users. The evaluation refuses to proceed on untrusted input, ensuring workflow safety during issue triage.

Automated issue plan evaluation requires trusted-authored implementation plan comments to proceed and relies on read-only repo context checks. It will refuse evaluation on untrusted input and cannot validate plans without explicit pipeline configuration access.