ideatelisted

# Ideate One skill, two phases. Phase 1 (cycle-check) always runs and is cheap. Phase 2 (ideation) runs only when the previous batch is fully complete, so batches are strictly sequential: ideate 4-5 → implement all → ideate again. **State lives in GitHub only** — the open `ideation-batch` issue and its task-list are the single source of truth. No local state files (cloud and local sessions must see the same state). ## Hard rules - **Never add the `ready` label to a `feature-proposal` issue.** The implement-queue claims by `ready` and would try to implement an un-decomposed proposal. `ready` belongs only to the children `/decompose` creates. Defensively strip `ready` from any `feature-proposal` issue you see. - **Never fetch live site URLs** — cloud routines have no egress (docs/scheduled-tasks.md). Grounding = tracked files + `gh` only. - **Never re-propose a vetoed idea** — vetoes are permanent dedup memory. - Labels used: `feature-proposal`, `ideation-batch`, `vetoed`, `deferred` (create-if-missing with `gh label create` before first use). ## Flags | Flag | Effect | | ------------------ | ------------------------------------------------------------- | | `--window-hours N` | Override the 66h veto window (testing only; e.g. `0`) | | `--dry-run` | Report what would happen; create/edit/close nothing on GitHub | ## Phase 1: Cycle-check (always) ### 1. Find the current batch ```