cf-plan-resumelisted

# /cf-plan-resume > **CLI Requirement:** NONE — Works without `coding-friend-cli`. Reads the plan file and its context file directly and dispatches cf-implementer; no CLI features are required. See [CLI requirements](../../../docs/cli-requirements.md) for the full matrix. Resume the implementation plan at: **$ARGUMENTS** (a plan folder path, an entry file path, or a bare `<slug>`). ## Workflow ### Step 0: Custom Guide Custom guide — auto-loaded below (if the raw command shows instead of its output, run it yourself): ```! bash "${CLAUDE_PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-plan-resume ``` If output is not empty, integrate returned sections: `## Before` → before first step, `## Rules` → apply throughout, `## After` → after final step. ### Resume Protocol 1. **Resolve the plan entry file**: - Full path to a folder → use `<folder>/README.md`. Full path to a file → use it directly. Validate the target is within the current working directory or `{docsDir}`; report error and stop if outside. - Name only (`<slug>`) → first, reject the argument outright if it contains `/`, `\`, or `..` (report: "Invalid plan name — slugs cannot contain path separators or `..`." and stop). This must happen BEFORE constructing any candidate path, since the candidates below are built by directly interpolating `<slug>` — a slug containing `../` would otherwise escape `{docsDir}/plans/`. Once the slug passes this check, resolve in this order, using the first that exists: `{docsDir}/plan