monthlisted

# /month **Input:** the plan text pasted or attached in the same message as `$ARGUMENTS` (or the attached file's content). ## Steps 1. **First-run setup** (only if no `.git` directory exists yet at the project root): - **Environment check first.** Verify `git --version`, `python3 --version`, and that `pytest` is importable (`python3 -c "import pytest"`). If any is missing, tell the user plainly what's missing and how to install it (e.g. `pip install -r requirements.txt --break-system-packages` for pytest) *before* proceeding — don't let a missing tool surface confusingly three steps later inside `/done`. - `git init` - Create `.gitignore` (venv, `__pycache__/`, `*.pyc`, `.pytest_cache/`, `.DS_Store`, `*.egg-info/`, `node_modules/`) if missing. - Create `requirements.txt` starting with `pytest` if missing. - Note in `CLAUDE.md` (create if missing, per the project's `CLAUDE.md` template) that dependencies are installed via `pip install -r requirements.txt`. - Run `git config core.hooksPath .githooks` so the schema-enforcement pre-commit hook (`.githooks/pre-commit`, which runs `scripts/validate_state.py`) is actually active for this repo — `.git/hooks/` itself isn't version-controlled, so this has to be set explicitly on first setup. - Initialize `state.json`'s top level: `schema_version: 2`, `badges_unlocked: []` (see `STATE_SCHEMA.md`'s "Motivation: badges" section). - `git add -A && git commit -m "Initial project setup"`. 2. **Ask about this month