issue-driven-workflowlisted

# Issue-Driven Workflow ## Philosophy The plan and Issue CSV are a **work amplifier**. Front-load the thinking so the agent has a full plate of actionable work to execute autonomously — more rows means more useful work per run. 1. **Planning (interactive)** — search the web, read docs, ask questions, gather context. A thorough plan means more work the agent can do without stopping. 2. **Execution (autonomous)** — be proactive, not passive. Work through the CSV end-to-end. Maximize useful work per run — don't wait for permission on routine decisions. The quality bar: every CSV row should be completable, testable, and markable DONE without further clarification. ## E2E loop plan → issues → implement → test → review ## Planning (interactive) 1. Restate the task and assumptions. 2. **Gather context** — search the web, read project files, inspect dependencies. Make every plan section concrete, not aspirational. 3. Ask up to 2 clarification questions if unclear, then proceed with stated assumptions. 4. Draft the plan in chat using `assets/_template.md`. Choose complexity (`simple|medium|complex`). 5. Ask: "Reply CONFIRM to write the plan file." 6. On confirmation: ```bash python3 .codex/skills/issue-driven-workflow/scripts/create_plan.py \ --task "<title>" --complexity <simple|medium|complex> ``` 7. Do not edit code while planning. ## Creating the CSV (interactive) 1. Generate after the plan is approved. 2. Break the plan into granular, independently actiona