m_plan_implementlisted
Install: claude install-skill mapuamap/denys-fast-mskills
# m_plan_implement
Follow-up to `m_plan`. Reads existing artifacts, drives them to completion. No re-planning. Default mode: direct walk. `/goal` mode: opt-in.
## Inputs
- `$ARGUMENTS`: optional task slug. If absent, auto-detect.
## Phase A — Load the plan
1. **List** `.m_plan/*/` directories.
- None → `No plans found. Run /m_plan first.` Stop.
- One → use it.
- Many → list with last-modified, ask via `AskUserQuestion` (max 4; on overflow, ask user to type the slug; if that tool is unavailable in this harness, ask in chat as a numbered list and wait).
2. **Read present files.** A plan is valid with at minimum `01_architecture.md`, `04_implementation_requirements.md`, `05_step_plan.md`, `09_verification.md`. Other files are optional — treat missing as N/A. Read whichever subset exists in parallel.
3. **Extract:**
- Step IDs S01..S<N> + per-step check commands from `05`.
- Verification rows V-* + current state from `09`.
- Build / test commands from `07_test_plan.md` if present, else from `CLAUDE.md`.
- Smoke + e2e IDs from `08_e2e_plan.md` if present.
- Deploy steps, real target hosts/services, release commands, rollback commands, and post-deploy smoke probes from `06_deploy_plan.md` if present.
- If `06` is missing or does not name a real target, inspect repo-local ops docs (`AGENTS.md`, `CLAUDE.md`, `README`, `docs/`, deploy scripts, compose/k8s/systemd files) for an unambiguous deploy path. If still ambiguous, mark deploy as blocked. Do not