planning-with-files
v0.1.0Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks,...
⭐ 0· 37·0 current·0 all-time
by@lnj22
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Manus-style file-based planning) match the included templates, helper scripts, and SKILL.md instructions. Required resources are minimal (templates and two small scripts) and appropriate for creating/maintaining task_plan.md, findings.md, and progress.md.
Instruction Scope
SKILL.md restricts actions to reading/writing/updating local planning files and prescribes reading plans before decisions and writing after searches. Hooks run benign commands (echo, cat head of task_plan.md) and the Stop hook invokes the included check-complete.sh to validate local plan completion. The instructions do not ask the agent to read unrelated system files or access external endpoints beyond normal WebSearch/WebFetch usage described.
Install Mechanism
No install spec is provided (instruction-only), so nothing is downloaded or installed. The code files are small local helper scripts and templates; no remote fetch or archive extraction occurs.
Credentials
The skill declares no required environment variables, credentials, or config paths. The scripts act on files in the current project directory and the skill directory only, which is proportional to the stated purpose.
Persistence & Privilege
always is false and the skill does not request elevated system privileges or modify other skills' configs. It will create/modify planning files in the user's project directory and run included scripts from the skill root — expected behavior for a planning helper.
Assessment
This skill appears to do what it says: it provides templates and small helper scripts to manage three planning files in your project directory and includes hooks that print status and run a local completion check. Before installing, review the templates and the two scripts (init-session.sh and check-complete.sh) to confirm you are comfortable with files being created/updated in your current working directory. There are no network callbacks, no requested secrets, and no remote install steps. If you keep sensitive data in the project folder, avoid running init-session.sh there or review/modify the templates to exclude sensitive content.Like a lobster shell, security has layers — review code before you run it.
latestvk977kmdraj9h1g4dn5xeeq1rt984wf26
License
MIT-0
Free to use, modify, and redistribute. No attribution required.