adhoc-attempt-project

name	adhoc-attempt-project
description	Use only when explicitly invoked to attempt a benchmark/project from its initial and update prompts without reading surrounding source. Given $ARGUMENTS identifying the prompt location, read the initial prompt, implement it in a fresh isolated directory, then read the update prompt and implement the requested updates.

adhoc-attempt-project

Given $ARGUMENTS, do not inspect the repository, benchmark directory, existing solution directories, tests, package files, or any other context beyond the two prompt files described here.

Prompt Files

If $ARGUMENTS is a directory, use:

• Initial prompt: $ARGUMENTS/initial-prompt.txt
• Update prompt: $ARGUMENTS/update-prompt.txt

If $ARGUMENTS explicitly provides two file paths, treat the first as the initial prompt and the second as the update prompt.

If the prompt paths cannot be determined from $ARGUMENTS without listing or reading other files, stop and ask for explicit prompt paths.

Workflow

1. Read only the initial prompt.
2. Create a new implementation directory with a name that is hard to confuse with existing project contents, such as adhoc-attempt-project__<safe-argument-name>__<timestamp>.
3. Implement the initial prompt inside that new directory. Do not read any files outside that new directory except the initial prompt.
4. After the initial implementation is complete, read only the update prompt.
5. Implement the update prompt inside the same new directory. Do not read any files outside that new directory except the update prompt.
6. Run only commands that operate on the new implementation directory or on files created inside it.

Do not copy, import, open, inspect, summarize, or compare against any existing source, tests, configs, lockfiles, result directories, or sample implementations.