Projects

What This Skill Does

The Projects skill transforms OpenClaw into a sophisticated project management assistant. It is designed to help users move from vague intentions to concrete, organized workflows. By establishing a standard structure within your ~/projects/ directory, the skill ensures that every goal has a defined path to completion. It handles initial scoping through a mandatory definition of 'done,' tracks granular tasks, organizes research in documentation files, and manages the lifecycle of a project from initiation to archiving. The agent actively monitors for stalled projects and prompts regular reviews, preventing the accumulation of 'zombie' work that drains mental bandwidth.

Installation

To integrate this system, run the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/projects

Use Cases

• Complex Home Improvements: Managing renovations where dependencies between contractors and material procurement are high.
• Learning & Skill Acquisition: Tracking progress in new languages or coding frameworks by separating research notes from actionable exercises.
• Freelance & Client Work: Maintaining a clear record of deliverables, deadlines, and project milestones while keeping client communication documented.
• Personal Goal Tracking: Planning long-term objectives like fitness transformations or travel planning where a clear end state defines success.

Example Prompts

1. "I want to start a project to learn Rust. Can you help me set up the workspace and define the first few tasks?"
2. "Add a task to the kitchen-renovation project: call the local cabinet manufacturer for a price quote."
3. "Run a weekly project review—which of my active projects have been stalled for more than two weeks?"

Tips & Limitations

• Maintain Focus: The system recommends keeping only 3-5 projects 'active.' Anything beyond this should be moved to the _someday folder to maintain focus.
• Avoid Vague Tasks: The agent enforces concrete, actionable task language. Avoid "research renovation" and use "call three contractors for quotes" instead.
• Embrace Termination: Do not be afraid to kill projects. If a project hasn't progressed in two weeks, use the review cycle to either move it to _someday or archive it entirely. Keeping projects alive that you don't intend to finish creates cognitive clutter.
• Scalability: For large projects, manually move to a multi-phase folder structure once you cross the 15-task threshold.