devlisted

# /mneme:dev — Drive the mneme workflow engine through development phases Thin dispatcher over the mneme workflow engine. It starts (or resumes) a run, parses the engine's flat-text response, branches on the single actionable directive, does exactly what that directive's payload asks, submits a matching StepResult, and loops until a terminal. All sequencing, gates, retries, and recall live INSIDE the engine (`workflow_start` / `workflow_step`). This skill adds ZERO orchestration: one branch per directive kind, each rendering its instruction from the directive PAYLOAD only. If a branch is ever forced to infer or fetch data outside the directive, that is engine-code debt — record it, never thicken this markdown. ## Arguments — MULTI-PHASE-INPUT The run needs `phases: string[]` — ONE OR MORE markdown phase-document texts. The skill assembles that array from the argument, which takes one of the forms below, plus an OPTIONAL `until <phase-id>` boundary appended at the very end. ### SLUG-RESOLVE — how the argument becomes a phase folder The project's CORPUS is derived from the cwd: the repo root's absolute path with every `/` replaced by `-` (leading `-` included) names `~/.mneme/<project-slug>/`, and TASK directories live under its `workflow/` subdirectory — one `<spec-slug>/` folder of `phase-*.md` files per task (what migrate emits). Resolve the argument in this order: - **slug** (the preferred form): `/mneme:dev <slug> [until <id>]` — a bare name that is neither an exi