← ClaudeAtlas

planslisted

Manage the plans/ spec-driven planning system. Use `init` to bootstrap plans/ in a project, `sync` to audit drift between plan files and git, `new` to create a plan file, `update` to refresh system files. Invoked as /plans:plans (plugin) or /plans (project-local).
yrangana/Plans · ★ 4 · Data & Documents · score 72
Install: claude install-skill yrangana/Plans
# /plans Four modes. Invoke as `/plans:plans <mode>` (plugin install) or `/plans <mode>` (project-local install). ```text init bootstrap plans/ in this project from the bundled template sync audit plans/ for drift, regenerate derived files, propose fixes new guided creation of a new plan file with correct structure update refresh system files (roadmap.html, plans/README.md) from the installed version ``` If invoked with no argument or an unrecognized one, list the four modes and ask which is wanted. ## Delivery detection Every mode needs to know whether a bundled template is reachable, not merely which directory this skill copy lives in. Determine it once, from the absolute path of this SKILL.md: 1. Resolve the plugin root: walk up from this file's directory until an ancestor directory directly contains a `template/` subdirectory. That ancestor is the plugin root. 2. Check whether `<plugin-root>/template/plans/` exists. - Found: **BUNDLED** delivery. The bundled template is at `<plugin-root>/template/plans/`. This covers both a real marketplace install (the plugin root sits under `.../plugins/cache/...`) and a local checkout loaded with `claude --plugin-dir <path>` (the plugin root is the checkout itself). Invocation spelling for messages: `/plans:plans`. - Not found (`<plugin-root>/template/plans/` does not exist, whether because no ancestor contains a `template/` directory at all, or an ancestor's `template/` exists but has no `plans/` subdirectory, as