Projects

Build a personal project management system that scales from simple lists to structured planning.

Iván

@ivangdavila

What This Skill Does

A personal project management system that organizes projects into folders with README, tasks, and notes. It helps define success criteria, capture concrete tasks, detect stalled projects, and archive completed work — scaling from simple lists to phased milestones.

Replaces scattered notes and ad-hoc task tracking by providing a lightweight, file-based system that enforces clear scope, regular reviews, and healthy project limits.

When to Use It

  • Start a new project by defining its scope and success criteria
  • Capture a concrete task for an existing project
  • Review stalled projects and decide whether to park or kill them
  • Archive a completed project with a lessons-learned note
  • Set up a phased structure for a large project with multiple workstreams
  • Create a template for recurring client projects

Install

$ openclaw skills install @ivangdavila/projects

Core Behavior

  • 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

First Question

  • "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

Project Types to Recognize

  • 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

Minimal Project Structure

  • 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

When User Starts a Project

  • 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

Task Capture

  • 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

When Projects Grow

  • 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

Phase/Milestone Structure

For larger projects:

~/projects/kitchen-renovation/
├── README.md
├── phase-1-planning/
│   ├── tasks.md
│   └── notes.md
├── phase-2-demo/
├── phase-3-install/
└── archive/

Active Project Limits

  • 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

Weekly Project Review

  • 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?

Stalled Project Detection

  • 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

Project Completion

  • 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

Client/Work Projects

  • 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

What NOT To Suggest

  • 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

Project Templates

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

Integration Points

  • Calendar: deadlines, milestones
  • Contacts: collaborators, stakeholders
  • Invoices: if client project with billing
  • Goals: projects often serve larger goals

Someday/Maybe List

  • 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

Project Metrics (When Asked)

  • How long did similar projects take?
  • Completion rate: started vs finished
  • Average project duration
  • Don't track obsessively — only if user finds it useful

Related skills

Trello

@byungkyu

Trello API integration with managed OAuth. Manage boards, lists, cards, members, and labels. Use this skill when users want to interact with Trello for project management. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).

717k

ClickUp

@shubhs0707

Interact with ClickUp project management platform via REST API. Use when working with tasks, spaces, lists, assignees, or any ClickUp workflow automation. Handles pagination, subtasks, and common query patterns. Use for task management, reporting, automation, or any ClickUp-related queries.

114.9k

Project Management Guru (ADHD)

@mikecourt

Expert project manager for ADHD engineers managing multiple concurrent projects. Specializes in hyperfocus management, context-switching minimization, and parakeet-style gentle reminders.

53.5k

Decision Trees

@evgyur

Decision tree analysis for complex decision-making across all domains. Use when user needs to evaluate multiple options with uncertain outcomes, assess risk/reward scenarios, or structure choices systematically. Applicable to business, investment, personal decisions, operations, career choices, product strategy, and any situation requiring structured evaluation. Triggers include decision tree, should I, what if, evaluate options, compare alternatives, risk analysis.

134.9k

Notion Sync

@robansuini

Bi-directional sync and management for Notion pages and databases. Use when working with Notion workspaces for collaborative editing, research tracking, proj...

65.0k

Notebook

@thesethrose

Local-first personal knowledge base for tracking ideas, projects, tasks, habits, and any object type you define. YAML-based with no cloud lock-in.

83.9k