project_tasks

Create and manage persistent project tasks in .local/tasks markdown files.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/CatRabbit499/Digital_Portfolio --skill project-tasks-catrabbit499
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project_tasks
Source: https://github.com/CatRabbit499/Digital_Portfolio/tree/main/templatemo_600_prism_flux/projects/CS-240/Lab-Portfolio/Lab-Portfolio-Dec_8_2025/.local/skills/project_tasks
Command: npx skills add https://github.com/CatRabbit499/Digital_Portfolio --skill project-tasks-catrabbit499

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams and individuals struggle to coordinate long-running work without a persistent, user-visible plan. This skill provides a canonical place to define, track, and hand off high-level project tasks to agents while preserving progress across sessions.

Core Features & Use Cases

  • Persistent project tasks visible to users, allowing status updates and reference across conversations.
  • Milestone planning and handoffs to a main agent or task agents for execution while maintaining clarity on ownership.
  • User-facing progress communication to show milestones and status updates to stakeholders.

Quick Start

Create a new project task plan, save it to .local/tasks as a markdown file, and propose the task 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 multiple sessions?

Persistent project tasks are saved as markdown plan files in the .local/tasks directory. This allows you to create, track, and reference high-level milestones across multiple sessions while maintaining progress visibility.

How do I coordinate task handoffs to agents for project planning?

You coordinate task handoffs by proposing high-level milestones through an approval workflow. Once approved, you can hand off these persistent tasks to a main agent or task agents for execution while retaining clear ownership tracking.

Can I use an approval workflow for proposing project tasks?

Yes, an approval workflow is supported for proposing project tasks. You can create a task plan, save it to .local/tasks, and propose it directly to the user for review before execution begins.

Does this approach require task identifiers for milestone tracking?

Task identifiers are supported to help you manage and track user-visible project milestones. They provide a canonical reference point for coordinating handoffs and status updates within your collaborative workflow.

What is the best way to show project progress to stakeholders?

The best way to show progress is through user-facing milestone communication. By maintaining persistent project tasks, you can provide stakeholders with clear status updates and visibility into high-level milestones over time.