new-idealisted

Start the validation pipeline for a new SaaS idea. Raw idea from the user: $ARGUMENTS ## Steps 1. Load the `method-rules` skill (Skill tool) — its rules govern everything that follows. Then load the `method-rules-state-schema` skill (Skill tool) — never read schema files off disk; they ship as skills precisely so a marketplace install has no filesystem dependency outside your workspace. 2. If `$ARGUMENTS` is empty, ask the user for the raw idea (one message is enough — vague is fine, clarifying it IS the pipeline's job). 3. Derive a short kebab-case slug **from the idea's content** — never from the working directory's name. If the two would coincide, say so and confirm, then record in `README.md` and `idea-brief.md` that the slug is a folder handle and **not** a product name or a positioning decision. (Run #3 silently adopted the repo folder name as the slug and carried an unmade branding decision into every artifact until the founder caught it.) If `ideas/<slug>/` already exists in the current workspace, ask whether to resume it (then use the status skill) or pick a new slug. 4. Create `ideas/<slug>/` with: - `state.json` in the **exact v1.3 shape from the `method-rules-state-schema` skill** (defaults; `mode: "analysis"`, `market_shape: "single-sided"`, `sides: []` — stage 0.3b re-classifies with the founder; never pre-assign a shape, `active: ["0.0"]`; `cycles: [{"id":"C1","status":"framing","parent":null,"state":null}]`, `active_cycle: "C1"`, `maintenance`/`health_cr