Project and task management with Loom. Use when the user is working on a project, planning work, tracking tasks, or when you need to record progress, decisions, and blockers.
Manages projects and tasks by tracking progress, creating notes, and logging blockers automatically during development work.
npx claudepluginhub jake-mok-nelson/loomThis skill inherits all available tools. When active, it can use any tool Claude has access to.
You have access to a Loom MCP server that stores projects, tasks, problems, goals, outcomes, and task notes in a local SQLite database. Use it proactively to keep work organised as you go — don't wait for the user to ask you to update Loom.
The top-level container. Every task and outcome belongs to a project. Problems and goals can optionally link to a project.
Fields: name (required), description, external_link (e.g. a Jira or GitHub URL).
Units of work inside a project.
Fields: project_id (required), title (required), description, task_type (general | chore | investigation | feature | bugfix), status (pending | in_progress | completed | blocked), priority (low | medium | high | urgent), external_link.
Timestamped notes attached to a task. Use these to record progress, decisions, context, and findings as work happens.
Fields: task_id (required), note (required).
Issues or blockers, optionally linked to a project and/or task. A problem linked to a task must belong to the same project. Problems support many-to-many relationships with projects via link_problem_to_project.
Fields: title (required), project_id, task_id, description, status (open | in_progress | resolved | blocked), assignee (optional - use to link problems to a person, e.g., a superior's ID or email).
Objectives optionally linked to a project and/or task. A goal linked to a task must belong to the same project. Goals support many-to-many relationships with projects via link_goal_to_project, allowing you to share goals across projects or link your goals to those of your superiors.
Fields: title (required), project_id, task_id, description, goal_type (short_term | career | values | requirement), assignee (optional - use to link goals to a person, e.g., your manager or superior).
Results or milestones linked to a project (required) and optionally a task. A task must belong to the same project.
Fields: project_id (required), title (required), task_id, description, status (open | in_progress | completed | blocked).
Goals and problems can be linked to multiple projects using junction tables:
link_goal_to_project / unlink_goal_from_project to manage goal-project relationshipslink_problem_to_project / unlink_problem_from_project to manage problem-project relationshipsget_goal_projects / get_project_goals to query goal-project linksget_problem_projects / get_project_problems to query problem-project linksThis allows you to:
assignee fieldBoth goals and problems now support an optional assignee field:
list_goals or list_problems with the assignee parameterFollow these conventions automatically throughout the conversation. Do not wait for the user to tell you to update Loom.
update_task to set its status to in_progress.create_task first, then mark it in_progress.blocked.resolved and unblock the task (set it back to in_progress).update_task to set its status to completed.Choose the right task_type when creating tasks:
feature — new functionalitybugfix — fixing broken behaviourchore — maintenance, dependency updates, config changesinvestigation — research, spikes, understanding a problemgeneral — anything that doesn't fit the aboveSet priority based on impact and urgency:
urgent — blocking other work or users right nowhigh — important and should be done soonmedium — normal priority (default)low — nice to have, no time pressureWhen the user mentions a GitHub issue, Jira ticket, or any external reference, store it in external_link on the relevant project or task.
list_tasks with filters (project_id, status, task_type) rather than get_task in a loop.list_problems and list_outcomes with filters similarly.list_goals with filters (project_id, task_id, goal_type, assignee) to find specific goals.list_projects / list_tasks.Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.