ultracode-verifylisted

# UltraCode Verify ## Respect explicit Help precedence If the request explicitly invokes `$ultracode-help` or `ultracode-help`, do not inspect, create, execute, or update a verification plan. Read `../ultracode-help/SKILL.md` and answer `verify` as a read-only Help topic. Create and maintain feature-level functional verification as a durable project artifact. Read `../ultracode/references/feature-verification.md`, `../ultracode/references/feature-verification-plan.schema.json`, and `../ultracode/references/command-interface.md` completely before acting. ## Select the operation Classify the request as one or more of: - **Create:** derive acceptance criteria and scenarios, preview the exact plan path and content, then write only when the current request and project control authorize it. - **Inspect:** validate and explain an existing plan read-only. - **Execute:** run only the authorized local scenarios, record direct evidence, and append results. - **Record:** append a supplied result only after checking that its evidence supports that status. - **Reconcile:** detect stale, incomplete, contradictory, duplicated, or orphaned plan content without silently repairing it. - **Summarize:** derive the current feature outcome from the latest scenario results without changing the plan. Never create or update a plan merely because another command mentions validation. A durable write requires an explicit verification-plan request or already-authorized feature work whose task