ck:project-management

Manage Claude Tasks with persistent plan files for cross-session project oversight.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/mafvietnam/mafapp --skill ck-project-management-mafvietnam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:project-management
Source: https://github.com/mafvietnam/mafapp/tree/main/.claude/skills/project-management
Command: npx skills add https://github.com/mafvietnam/mafapp --skill ck-project-management-mafvietnam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Project oversight across multiple plans and sessions by using Claude native Tasks together with persistent plan files to maintain state, progress and accountability beyond a single session.

Core Features & Use Cases

  • Cross-session planning and progress tracking with task hydration
  • Status updates, report generation, and documentation coordination
  • Seamless plan-file synchronization and integration with plan metadata

Quick Start

Provide a plan directory and run a session to hydrate tasks and begin tracking progress.

Frequently Asked Questions about ck:project-management

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

FAQPage Schema
How do I track project progress across multiple Claude sessions?

You can maintain progress tracking across sessions by using persistent plan files that hydrate Claude Tasks, ensuring state and accountability are preserved when a session ends.

What is task hydration in cross-session project planning?

Task hydration in cross-session project planning is a workflow that restores task state from persistent plan files, allowing Claude to resume oversight and update progress without losing context.

How do I generate status updates and documentation for multiple project plans?

Generate status updates and documentation by applying TaskList and TaskGet operations across multiple plans, using documentation triggers to coordinate reporting and sync metadata back to plan files.

Can I use this project management workflow without CLI tooling?

You can use this workflow without CLI tooling because it includes a TodoWrite fallback that activates when CLI-only TaskCreate and TaskUpdate tools are unavailable in your environment.

What's the best way to synchronize plan files with task progress?

The best way to synchronize plan files with task progress is through the plan-sync-back mechanism, which updates persistent plan files with current task status during the hydration workflow.