Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
Planning with Files Work like Manus: Use persistent markdown files as your "working memory on disk." Quick Start Before ANY complex task: 1. Create in the working directory 2. Define phases with checkboxes 3. Update after each phase mark [x] and change status 4. Read before deciding refresh goals in attention window The 3 File Pattern For every non trivial task, create THREE files: | File | Purpose | When to Update | | | | | | | Track phases and progress | After each phase | | | Store findings…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/planning-with-files · pinned to the source commit
# Run from your project root
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/33-Galaxy-Dawn-claude-scholar/skills/planning-with-files" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/33-Galaxy-Dawn-claude-scholar/skills/planning-with-files" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/planning-with-files
Scanner static-checks@0.1.0 · commit 692e9fa3fea4. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.