Yolo

# Execute all open tasks in YOLO mode

This mode is meant to be run without user interaction.
You **DO NOT** ask the user any questions or ask for confirmation
If in doubt you **RESEARCH** and **ULTRATHINK** about the best solution.

**IMPORTANT** you try not to stop at any certain point but do so if you need after thoughtful consideration.

Priority is to get the work completed.

## Mode Selection

Check <$ARGUMENTS>:

- If sprint ID provided (e.g., S03): Work ONLY on that sprint
- If empty: Work on general tasks first, then active sprint tasks

**Report Mode** to the User!

## Safety Guidelines

- **NEVER** modify critical files (.env, alembic migrations, production configs)
- **STOP** if you encounter database schema changes
- **STOP** if you need to delete more than 5 files
- **STOP** if tests are failing after your changes
- **ALWAYS** run tests after implementing a task

## Follow this exact process

You need to stick to this process and **PRECISELY** follow it

Before you start:

- Run tests to ensure clean baseline: `poetry run python run_dev.py test`
- Check git status to ensure clean working directory

If any of these fail, exit right away report to the user.

Also consider <$ARGUMENTS> - if anything between <> can be considered additional instructions, prioritize them in the process.

Get the current datetime stamp from the system and remember it

### FIND OPEN WORK

Execute based on mode:

**If Sprint ID provided in arguments:**

- Navigate to .simone/03_SPRINTS/{sprint_id}/
- Check if sprint has tasks (T*.md files)
- If NO tasks exist:
  - Check for sprint meta file
  - If meta exists: Jump to ### CREATE SPRINT TASKS
  - If no meta: Exit with error - sprint doesn't exist
- If tasks exist: Continue to **Task selection** section below

**If NO arguments (general mode):**

- Use PARALLEL SUBAGENTS to check:
  - .simone/04_GENERAL_TASKS for open general tasks
  - .simone/00_PROJECT_MANIFEST.md for currently active sprint
  - .simone/03_SPRINTS/ for any sprint with only meta file
- Priority order:
  1. General tasks (if any open)
  2. Active sprint tasks (if any open)
  3. Sprint needing task creation (if found) - maintain order of Sprints

**Task Selection:**

- From found tasks, select ONE that is not completed. Take the lowest ID in Sprint or General Tasks
- Skip tasks you've previously attempted (check OUTPUT LOG)
- If no suitable task found and no sprint needs tasks: Exit gracefully

### CREATE SPRINT TASKS

**ONLY EXECUTE** if sprint needs task creation

- Use a **SUBAGENT** and have it include @.claude/commands/simone/create_sprint_tasks.md with Sprint ID as argument
- Wait for completion
- After task creation move back to `### FIND OPEN WORK`

### WORK ON TASK

- if you have touched this task before ignore it and jump to the next task
- if you can't find a task that you have not tried fixing before jump to ### EXECUTE PROJECT REVIEW
- if you find a task that you cannot fix because the work was done already, close the task and note in Output Log of task.
- **BEFORE STARTING**: Create a git branch for the task: `git checkout -b task/<task-id>`
- **USE A SUBAGENT** and have it include @.claude/commands/simone/do_task.md with the Task ID as Argument to execute the Task.
- **AFTER TASK COMPLETION**: Run tests to verify nothing broke: `poetry run python run_dev.py test`
- on any failure in the task execution assess the severity of the error:
  - CRITICAL errors (breaking tests, security issues, data loss risk): **FIX PROBLEMS**
  - NON-CRITICAL errors (linting, formatting, minor issues): note in OUTPUT LOG and continue
- on success move on

### COMMIT WORK

- **ONLY IF** tests are passing and no critical issues exist
- **USE A SUBAGENT** and have it include @.claude/commands/commit.md with the Task ID as Argument and YOLO as additional argument
- on any failure when committing, note the problem in the OUTPUT LOG of the task and continue
- after successful commit, merge to main: `git checkout main && git merge task/<task-id>`
- on success move on

### REPEAT FOR ALL OPEN TASKS

**Based on current mode:**

**Sprint-specific mode:**

- Continue with next task in the specified sprint only
- Go back to ### WORK ON TASK until all sprint tasks are done
- When sprint is complete, move to project review

**General mode:**

- After completing a general task, check for more general tasks first
- If no general tasks remain, move to active sprint tasks
- Continue until all accessible tasks are done
- When done move on

## EXECUTE PROJECT REVIEW

- **USE A SUBAGENT** and have it include @.claude/commands/project_review.md
- Depending on the results of the review:
  - On FAIL: Think about possible fixes.
  - If fixes are quickly done, fix right away and repeat `## EXECUTE PROJECT REVIEW``
  - If fixes are more complex **USE A SUBAGENT** and have it include @.claude/commands/create_general_task.md to create new general tasks as needed.
  - Go back to `### FIND OPEN WORK` to work on these fixes
  - On PASS: move on

## MORE WORK TO DO?

**Based on current mode:**

**Sprint-specific mode:**

Your work is done. Move to `## CREATE SUMMARY`

**General mode:**

- Move on to check for more open Tasks or Sprints. Move to `### FIND OPEN WORK`

## CREATE SUMMARY

- Get current datetime stamp from the system and compare to initially remembered timestamp. Calculate duration of the process.
- Create a summary report including:
  - Mode executed (Sprint-specific or General)
  - Sprint tasks created (if applicable)
  - Number of tasks completed
  - Number of tasks skipped/failed
  - Total duration
  - Any critical issues encountered
  - Current test status
  - Next recommended action
- Report the result of the review to the user including the duration.

Your work is done. Thank you.