planning
v2.53.2Software implementation planning with file-based persistence (.plan/). Use when asked to plan, break down a feature, or starting complex tasks. Apply proacti...
⭐ 0· 50·0 current·0 all-time
byIlia Alshanetsky@iliaal
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe software implementation planning with on-disk .plan/ persistence; the only included code (init-plan.sh) and SKILL.md instructions are directly related to scaffolding, reading, and updating local planning files. No unrelated credentials, binaries, or network endpoints are requested.
Instruction Scope
SKILL.md instructs the agent to create/read/write files under .plan/, consult tests (grep/glob), and use git commands (e.g., git diff --stat, record commit SHAs). These actions are within scope for a planning/orchestration skill but do give the agent read/write access to repository files and expect git to be available. The instructions explicitly state `.plan/` is ephemeral and should not be committed.
Install Mechanism
No install spec and only a small included shell script (init-plan.sh). No downloads or external package installs; nothing will be written to disk by an installer beyond what the agent does at runtime via the script and plan files.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. The instructions reference local tools (git, grep) but do not demand unrelated secrets or cloud credentials—proportional to the stated purpose.
Persistence & Privilege
Skill is not always-enabled and does not request persistent platform privileges. It will create and write files under a repository-local `.plan/` and append `.plan/` to `.gitignore` (or create a .gitignore containing only `.plan/` if none exists). This is an expected, limited level of persistence for a planning helper.
Assessment
This skill appears to do what it says: scaffold and manage ephemeral planning files under .plan/ and guide planning workflow. Before installing, note: (1) it will create .plan/ and three template files and will add '.plan/' to .gitignore (if .gitignore doesn't exist the script will create one containing only '.plan/'); (2) the skill's instructions assume access to repository files and git—ensure the agent is allowed to read/write the repo and run git; (3) do not store secrets or sensitive data in .plan/ (the skill treats those files as ephemeral and non-committed); (4) there is no network or credential access requested by the skill. If you’re comfortable with an assistant that reads/writes planning files in your repo and records commit SHAs when you mark tasks done, this skill is coherent and appropriate.Like a lobster shell, security has layers — review code before you run it.
latestvk97ej02qkpyknvysymdbdr7g2d84fgw0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.