What problem does it solve? Losing track of a multi-file code change across sessions is common: you forget which files to touch, which symbols to edit, and what was already done. This Skill turns a desired change into a durable, resumable checklist stored at .opencode/plans/<slug>.md, so the plan survives across sessions and can be executed later on demand. ## Core Features & Use Cases - Three firewalled modes: PLAN writes the outline then hard-stops, RESUME reconciles the checklist against the live codebase without editing, and EXECUTE runs remaining steps only when the user literally says "execute <slug>". - Repo-grounded planning: reads AGENTS.md first, explores the codebase with grep/read or explore subagents, and anchors every step to a file, symbol, and approximate line range verified against the live tree. - Automatic archiving: when all steps are done and whole-change verification passes, it sets Status: complete and moves the plan into .opencode/plans/archive/ without overwriting existing archives. - Use Case: You ask to "plan adding caching to the validator". The Skill explores the repo, writes a numbered checklist of every file and symbol to change with per-step verification commands, then stops. Days later, in a new session, you say "execute add-validator-caching" and it reconciles what is already done, applies the remaining edits step by step, verifies each, and archives the completed plan. ## Quick Start Ask the assistant to plan a specific code change, for example: plan the steps to add request logging to the API handlers.
