"Work like Manus" — Uses persistent markdown files for planning, progress tracking, and knowledge storage.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplanning-with-filesExecute the skills CLI command in your project's root directory to begin installation:
Fetches planning-with-files from charon-fan/agent-playbook and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate planning-with-files. Access via /planning-with-files in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
27
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
27
stars
"Work like Manus" — Uses persistent markdown files for planning, progress tracking, and knowledge storage.
A Claude Code skill that transforms your workflow to use persistent markdown files for planning and progress tracking — the pattern that made Manus AI worth billions.
Claude Code (and most AI agents) suffer from:
For every complex task, create THREE files:
task_plan.md → Track phases and progress
notes.md → Store research and findings
[deliverable].md → Final output
1. Create task_plan.md with goal and phases
2. Research → save to notes.md → update task_plan.md
3. Read notes.md → create deliverable → update task_plan.md
4. Deliver final output
Use this pattern for:
Skip for:
This skill is typically installed globally at ~/.claude/skills/planning-with-files/.
From this repository:
ln -s /path/to/agent-playbook/skills/planning-with-files ~/.claude/skills/planning-with-files
If you prefer the standalone workflow, see the upstream repository in the Links section.
| Principle | Implementation |
|---|---|
| Filesystem as memory | Store in files, not context |
| Attention manipulation | Re-read plan before decisions |
| Error persistence | Log failures in plan file |
| Goal tracking | Checkboxes show progress |
| Append-only context | Never modify history |
You: "Research the benefits of TypeScript and write a summary"
Claude creates:
# Task Plan: TypeScript Benefits Research
## Goal
Create a research summary on TypeScript benefits.
## Phases
- [x] Phase 1: Create plan ✓
- [ ] Phase 2: Research and gather sources (CURRENT)
- [ ] Phase 3: Synthesize findings
- [ ] Phase 4: Deliver summary
## Status
**Currently in Phase 2** - Searching for sources
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
shadcn/improve
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
I recommend planning-with-files for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
planning-with-files fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
planning-with-files fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
planning-with-files is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
planning-with-files is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
planning-with-files reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: planning-with-files is focused, and the summary matches what you get after install.
planning-with-files has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: planning-with-files is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: planning-with-files is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 34