pm-done

Mark tasks, issues, and feature requests as completed with cascading state changes.

1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/pinkroosterai/PinkRoosterMcp --skill pm-done
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-done
Source: https://github.com/pinkroosterai/PinkRoosterMcp/tree/main/.claude/skills/pm-done
Command: npx skills add https://github.com/pinkroosterai/PinkRoosterMcp --skill pm-done

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of marking project tasks, issues, and feature requests as completed, automatically handling cascading state changes across linked entities.

Core Features & Use Cases

  • Task Completion: Mark individual tasks, issues, or feature requests as done.
  • Batch Completion: Complete multiple tasks within the same work package simultaneously.
  • Automated Cascading: Automatically propagates completion status to linked issues and feature requests when a work package is auto-completed.
  • Work Package Completion: Can batch-complete all non-terminal tasks within a specified work package.

Quick Start

Use the pm-done skill to mark task proj-1-wp-3-task-5 as completed.

Frequently Asked Questions about pm-done

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

FAQPage Schema
How do I mark project tasks and feature requests as completed with cascading status updates?

Marking project tasks and feature requests as completed triggers cascading state changes across linked work packages and dependent items, automatically propagating completion status to connected issues.

Can I batch complete multiple tasks within the same work package simultaneously?

Batch completing tasks within a work package automatically propagates completion status to linked issues and feature requests, handling cascading state changes without manual updates.

How does automated state propagation work for issues linked to auto-completed work packages?

Automated state propagation for issues linked to auto-completed work packages triggers cascading state changes across dependent items, marking linked issues and feature requests as completed.

What is the best way to complete all non-terminal tasks in a work package?

Completing all non-terminal tasks in a work package is handled through automated batch completion, which marks the specified work package tasks as done and triggers cascading state changes.

Do I need to manually update linked issues when a work package is auto-completed?

No, manual updates are unnecessary because auto-completing a work package automatically propagates completion status to linked issues and feature requests through cascading state changes.