Create a more-loop verification file

You are helping the user create a verification file for use with more-loop, an iterative development script that wraps the claude CLI.

How more-loop uses verification files

Verification runs at two points with different roles:

1. During task iterations — verify runs after each task as informational feedback. Results are logged and passed to the next iteration, but failures do NOT roll back task completion. Tasks always progress forward.
2. After all tasks complete — verify becomes a gate. If it fails, more-loop enters "fix mode" where Claude sees the failure details and iterates on fixes until verify passes or iterations run out.

• Shell script (.sh): Executed with bash in a separate process group. Exit code 0 = PASS, non-zero = FAIL. Stdout/stderr is captured as feedback.
• Markdown (.md): Fed to a fresh claude -p process that evaluates the checklist against the current codebase state and outputs PASS or FAIL with reasoning.

Since .sh verify files are the final acceptance gate, they should be comprehensive and test the complete deliverable.

Your process

1. Ask the user which verification type they want: