project_tasks

Create and manage persistent project tasks with taskRefs and lifecycle states.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/akhilksap2026/YMSNOW27032026 --skill project-tasks-akhilksap2026
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project_tasks
Source: https://github.com/akhilksap2026/YMSNOW27032026/tree/main/replit/.local/skills/project_tasks
Command: npx skills add https://github.com/akhilksap2026/YMSNOW27032026 --skill project-tasks-akhilksap2026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and manage persistent project tasks that are visible to the user, allowing tracking of deliverables and milestones across sessions.

Core Features & Use Cases

  • Persistently store tasks with titles, descriptions, and state, enabling progress tracking across sessions.
  • Reference tasks by short taskRef identifiers (e.g., "#1") for easy discussion and updates.
  • Use to plan, monitor, and communicate project milestones with users and stakeholders.

Quick Start

Create a plan file under .local/tasks/ and call bulkCreateProjectTasks to instantiate a task, then propose it for user approval.

Frequently Asked Questions about project_tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track project milestones across different sessions?

Track project milestones across sessions by creating plan files under .local/tasks/ and calling bulkCreateProjectTasks to instantiate tasks with persistent titles, descriptions, and lifecycle states for continuous progress updates.

How do I create and update tasks for collaborative project planning?

Create and update tasks by defining them in a plan file, calling bulkCreateProjectTasks to instantiate them, and proposing them for user approval before updating their lifecycle states and task references.

What is a taskRef identifier and how does it work for project task management?

A taskRef is a short identifier like "#1" used to reference specific project tasks for easy discussion and updates. It links task entries to their lifecycle states within plan-file integrations for clear progress tracking.

Can I use plan files to organize user-visible project deliverables?

Plan files organize user-visible project deliverables by storing persistent tasks under .local/tasks/, allowing you to instantiate tasks via bulkCreateProjectTasks, update lifecycle states, and communicate milestone progress to stakeholders.

Do I need dependencies or external components to manage project workflows?

No dependencies or external components are required to manage project workflows. The task-management functions natively handle task creation, search, listing, updates, and plan-file integration without external libraries.

What is the best way to communicate project task progress to stakeholders?

Communicate project task progress to stakeholders by using persistent task states and short taskRef identifiers like "#1", enabling clear updates on deliverables and milestones across collaborative planning sessions.