phaselisted

# Phase Lightweight flipper for the `branches.lifecycle` key in `.ai-kit-setup`. Lives separate from `/ai:setup` so the user can change phase without walking the whole setup tree. ## When to use - User says "set this to production" / "we shipped, flip to prod" / "back to dev mode for the rewrite" - User asks "what phase are we in" / "is this dev or prod" - After a project gains real users (greenfield → mature transition) - Before a major rewrite that needs reset-friendly defaults For a full re-setup walkthrough use [`/ai:setup`](../setup/SKILL.md). For background on why this signal exists see [`standards/rules/project-lifecycle.mini.md`](../../../standards/rules/project-lifecycle.mini.md). ## Run ```bash bash "${AI_KIT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/bin/ai-kit-phase.sh" [development|production] ``` - No arg → prints current phase (default `production` when key missing). - `development` or `production` → writes the key and reminds the user to restart the session so the canonical rule re-emits. - Anything else → script exits non-zero with a clear error; marker is not touched. ## Output contract Read the script output back to the user: - If they asked for current phase, surface the single-word line. - If they flipped, surface the `lifecycle: <old> → <new>` line **and** the restart reminder. Do not skip the reminder — the rule is loaded once per session and the user's current context still reflects the old phase. ## Side effects - Writes one key (`branches.lifecycle`) i