arrangelisted

<!-- Role: One-time setup that installs mumei into a project Input: user instruction Output: create .mumei/ directory + propose additions to CLAUDE.md / .claude/rules/ Principle: Never modify existing files without user consent (claude-md-improver pattern) --> # Arrange Set up `mumei` for the current project. This skill is run **once** per project. It: 1. Creates the `.mumei/` directory structure. 2. Detects existing `CLAUDE.md` / `.claude/rules/*.md`. 3. Proposes additions about mumei's expectations and applies them with explicit user approval. ## When to use - The user explicitly says "set up mumei", "install mumei in this project", or invokes `/mumei:arrange`. - The first time `/mumei:proceed` is invoked in a project where `.mumei/` does not exist (route to this skill first). ## Method ### Step 1 — Detect existing project memory Read all of: - `CLAUDE.md` (project root) - `.claude/CLAUDE.md` - `~/.claude/CLAUDE.md` (user-level, read-only) - `.claude/rules/*.md` - `AGENTS.md` (if present) Summarize what is currently in place. Do NOT modify anything yet. ### Step 2 — Create `.mumei/` directory and its `.gitignore` ```bash mkdir -p .mumei/specs .mumei/archive .mumei/scratch [[ -f .mumei/current ]] || : > .mumei/current # empty until first feature ``` Generate `.mumei/.gitignore` so team-shared spec content (requirements / design / tasks / spec-reviews / reviews / scratch / archive) is tracked, while per-developer state (`current` cursor, `state.json` progress) i