Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Planning With Files
File-based planning for complex tasks. Use persistent markdown files as working memory to survive context resets. Creates task_plan.md, findings.md, and progress.md. Use for any task requiring >5 tool calls, research projects, or multi-step implementations.
skill openclawclawhub Free
File-based planning for complex tasks. Use persistent markdown files as working memory to survive context resets. Creates task_plan.md, findings.md, and progress.md. Use for any task requiring >5 tool calls, research projects, or multi-step implementations.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, templates/progress.md, templates/task_plan.md, templates/findings.md, scripts/init-session.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- wpank
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Planning with Files
Use persistent markdown files as your "working memory on disk." Based on context engineering principles from Manus.
OpenClaw / Moltbot / Clawbot
npx clawhub@latest install planning-with-files
WHAT This Skill Does
Treats the filesystem as persistent memory to overcome context window limitations. Three files track your state: FilePurposeUpdate Frequencytask_plan.mdPhases, progress, decisionsAfter each phasefindings.mdResearch, discoveries, decisionsAfter ANY discoveryprogress.mdSession log, test results, errorsThroughout session
WHEN to Use
Use for: Multi-step tasks (3+ steps) Research tasks requiring web search Building/creating projects from scratch Tasks spanning >5 tool calls Anything requiring organization across multiple files Tasks where losing context would cause rework Skip for: Simple questions Single-file edits Quick lookups Tasks completable in 1-2 actions Keywords: complex task, multi-step, research, build project, create application, plan, organize
The Core Pattern
Context Window = RAM (volatile, limited) Filesystem = Disk (persistent, unlimited) โ Anything important gets written to disk.
Phase 1: Create Planning Files
Before starting ANY complex task, create all three files in your project root: Create task_plan.md โ Copy from templates/task_plan.md Create findings.md โ Copy from templates/findings.md Create progress.md โ Copy from templates/progress.md
Phase 2: Execute with Discipline
Follow these rules during execution: The 2-Action Rule: After every 2 view/browser/search operations, IMMEDIATELY save findings to text files. Visual/multimodal content doesn't persist โ write it down before it's lost. Read Before Decide: Before major decisions, read your plan file. This keeps goals in your attention window after many tool calls. Update After Act: After completing any phase: Mark phase status: in_progress โ complete Log any errors encountered Note files created/modified Log ALL Errors: Every error goes in the plan file. This prevents repetition.
Phase 3: Handle Errors Systematically
The 3-Strike Protocol: ATTEMPT 1: Diagnose & Fix โ Read error carefully โ Identify root cause โ Apply targeted fix ATTEMPT 2: Alternative Approach โ Same error? Try different method โ Different tool? Different library? โ NEVER repeat exact same failing action ATTEMPT 3: Broader Rethink โ Question assumptions โ Search for solutions โ Consider updating the plan AFTER 3 FAILURES: Escalate to User โ Explain what you tried โ Share the specific error โ Ask for guidance Critical: if action_failed: next_action != same_action
Phase 4: Verify Completion
Use the 5-Question Reboot Test. If you can answer these, your context is solid: QuestionAnswer SourceWhere am I?Current phase in task_plan.mdWhere am I going?Remaining phasesWhat's the goal?Goal statement in planWhat have I learned?findings.mdWhat have I done?progress.md
Quick Reference: Read vs Write
SituationActionReasonJust wrote a fileDON'T readContent still in contextViewed image/PDFWrite findings NOWMultimodal โ text before lostBrowser returned dataWrite to fileScreenshots don't persistStarting new phaseRead plan/findingsRe-orient if context staleError occurredRead relevant fileNeed current state to fixResuming after gapRead all planning filesRecover state
Session Recovery
When starting a new session, check for previous work: # Check if planning files exist ls task_plan.md findings.md progress.md 2>/dev/null # If they exist, read them all before continuing cat task_plan.md findings.md progress.md If planning files exist from a previous session: Read all three files to recover context Run git diff --stat to see what changed Update planning files with any missing context Continue from where you left off
Templates
Copy these to start: templates/task_plan.md โ Phase tracking templates/findings.md โ Research storage templates/progress.md โ Session logging
Scripts
Helper scripts for automation: scripts/init-session.sh โ Initialize all planning files scripts/check-complete.sh โ Verify all phases complete
References
references/manus-principles.md โ Context engineering principles from Manus
Anti-Patterns
Don'tDo InsteadUse TodoWrite for persistenceCreate task_plan.md fileState goals once and forgetRe-read plan before decisionsHide errors and retry silentlyLog errors to plan fileStuff everything in contextStore large content in filesStart executing immediatelyCreate plan file FIRSTRepeat failed actionsTrack attempts, mutate approachCreate files in skill directoryCreate files in your project
NEVER Do
NEVER start a complex task without task_plan.md โ this is non-negotiable NEVER repeat a failed action exactly โ track what you tried, mutate the approach NEVER ignore errors โ log every error with resolution attempts NEVER rely on memory after >10 tool calls โ re-read your plan NEVER skip the 2-Action Rule for visual content โ multimodal data gets lost NEVER proceed past 3 failures without escalating โ ask the user for help NEVER create planning files in the skill directory โ they go in your project root
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
5 Docs1 Scripts
- SKILL.md
- README.md
- templates/findings.md
- templates/progress.md
- templates/task_plan.md
- scripts/init-session.sh