evolve-crux

# evolve-crux — ship a change to crux, rigorously This skill is for working **on crux the tool** (your clone of the crux repo), not on a research project that *uses* crux. It carries one change — a new capability or a fix for something crux keeps getting wrong — through a strictly gated arc: ``` ideate → build → validate → ship ``` Each stage has an **exit criterion**; you do not advance until it's met. The arc is the same whether the change is a one-line bug fix or a ROADMAP epic — only the ceremony scales. ## Who's driving (contributor-always) Assume **the person evolving crux is not the maintainer.** Because crux ships this skill to its users, everyone runs the *same* path and **ends at a pull request** — no auto-detection of who you are, no privileged branch. The maintainer is just the contributor who can **self-merge** their own PR, plus a small, separate **release** step (below). This keeps one code path and makes third-party PRs first-class. Work in a dedicated session **inside your crux clone** (a fresh chat, not the project you were researching). No clone yet — e.g. you installed the skills via `npx skills add`? `git clone https://github.com/mehdiforoozandeh/crux` first. For a large build you may dispatch a worktree sub-agent, but the default is the main thread. --- ## 1 · Ideate → a signed-off PRD ◆ Ideation ends when there is a **PRD** the human has approved — not before any code. Reach it by a **pingpong / grill-me back-and-forth** (surface one decision ...