Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Project management, tasks, milestones, and timesheets for ERPClaw
Project management, tasks, milestones, and timesheets for ERPClaw
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
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. Summarize what changed and any follow-up checks I should run.
User mentions a project โ help define scope, create folder User adds tasks โ capture in project context Regular review prompts โ surface stalled projects Create ~/projects/ as workspace
"What does done look like?" โ define success before starting Scope creep is the project killer โ clear boundaries from day one If they can't define done, the project isn't ready to start
One-time goal: clear end state, then archive (move apartments, plan trip) Ongoing area: never truly done, maintain indefinitely (health, career) Client work: external deadline, deliverables, often paid Learning: skill acquisition, may spawn other projects Creative: writing, art, building โ process matters as much as output
Folder with project name: ~/projects/kitchen-renovation/ README.md: what, why, done criteria, deadline if any tasks.md: simple checklist, add as discovered notes.md: decisions made, research, reference material
Ask: "What's the one sentence description?" Ask: "When does this need to be done?" (or "no deadline") Ask: "What's the very next physical action?" Create folder with README containing answers
Quick capture: "Add to kitchen project: call contractor" Tasks are concrete actions, not vague goals "Research options" is a task, "figure out renovation" is not Estimate size if useful: small/medium/large or hours
More than 15 tasks โ consider grouping into phases Multiple workstreams โ split into areas within project Dependencies emerging โ note which tasks block others Collaborators involved โ note who owns what
For larger projects: ~/projects/kitchen-renovation/ โโโ README.md โโโ phase-1-planning/ โ โโโ tasks.md โ โโโ notes.md โโโ phase-2-demo/ โโโ phase-3-install/ โโโ archive/
Suggest maximum 3-5 active projects โ more means nothing progresses Distinguish active (working this week) from someday (parked intentionally) Parked projects go in ~/projects/_someday/ Review someday quarterly โ activate, archive, or delete
What progressed this week? What's the next action for each active project? Any projects stalled more than 2 weeks? Any someday projects ready to activate?
No task completions in 2+ weeks โ surface in review Ask: "Is this still a priority? Block or drop?" Options: push forward, park to someday, kill it Killing projects is healthy โ better than zombie projects
Define done checklist in README from start When complete: review what went well, what didn't Archive to ~/projects/_archive/year/ Celebrate completion โ don't just move to next thing
Add: deadline, contact info, rate if applicable Track time if billing: simple log in project folder Deliverables list with status Communication log: key decisions and approvals
Complex project management app until files fail Rigid methodology (Agile, GTD, etc.) โ adapt to user Gantt charts for personal projects โ overkill Time tracking for non-billable work โ adds friction
Offer to create templates for recurring project types: "You start client projects often โ want a template?" Template: folder structure, README prompts, standard tasks Keep templates minimal โ adapt per project
Calendar: deadlines, milestones Contacts: collaborators, stakeholders Invoices: if client project with billing Goals: projects often serve larger goals
Ideas not ready for commitment Review monthly โ promote, delete, or keep parking No guilt about long lists โ it's a holding pen "This would be cool but not now" is valid
How long did similar projects take? Completion rate: started vs finished Average project duration Don't track obsessively โ only if user finds it useful
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.