Writing Plans
v0.1.0Use when you have a spec or requirements for a multi-step task, before touching code
⭐ 5· 5k·101 current·111 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (produce step-by-step implementation plans) align with the SKILL.md: it only asks the agent to create plan documents, list file paths, commands, and test steps. There are no unrelated environment variables, binaries, or install steps requested.
Instruction Scope
Instructions stay within planning: create plan files, enumerate exact file paths, provide code snippets, and include git/pytest commands and expected outputs. This is appropriate for an implementation-planning skill, but the SKILL.md explicitly requires embedding complete code and exact commands and references external sub-skills (superpowers:executing-plans, superpowers:subagent-driven-development). That increases the potential for subsequent automated execution (by other skills) — the plan itself does not perform I/O or network activity.
Install Mechanism
No install spec or downloaded code; instruction-only skills write nothing to disk by themselves. Lowest risk for install mechanism.
Credentials
Requires no environment variables, credentials, or config paths. Nothing disproportionate requested relative to the stated purpose.
Persistence & Privilege
always:false and default autonomous invocation are set (normal). The main consideration is that the skill instructs use of other sub-skills that may execute plans, run tests, and commit code — evaluate those sub-skills' privileges before enabling autonomous invocation. The skill itself does not request persistent or system-wide privileges.
Assessment
This skill is internally coherent and does not request secrets or installs. Before enabling it for autonomous use, verify the provenance and permissions of any referenced sub-skills (superpowers:executing-plans, superpowers:subagent-driven-development) because they are the components that would actually run commands or modify your repository. Prefer running it manually or in a dedicated worktree at first, review saved plan files (docs/plans/...) for accidental inclusion of secrets or sensitive file paths, and confirm any automated executors have limited, audited access to only the intended repository/worktree.Like a lobster shell, security has layers — review code before you run it.
latestvk97a1b1sjdresg5a8dkvxwhea180xz7p
License
MIT-0
Free to use, modify, and redistribute. No attribution required.