ck:project-management

Track project progress using plan files and Claude Tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured framework to manage multi-phase projects by coordinating plan files, Claude-native Tasks, and cross-session continuity, ensuring progress visibility and auditable records.

Core Features & Use Cases

  • Persistent plan files serve as the single source of truth for project progress across sessions.
  • Hydration of Claude Tasks from plan milestones to enable parallel work and resilience.
  • Progress tracking, status synchronization, and documentation coordination triggers to keep teams aligned.

Quick Start

Ask Claude to initialize a new project plan and begin hydrating tasks from your plan milestones.

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 multi-phase project progress across sessions?

Multi-phase project progress is tracked using persistent plan files as the single source of truth, ensuring cross-session continuity and auditable records. Claude Tasks are hydrated from plan milestones to synchronize status.

How do I coordinate plans and tasks for cross-session projects?

Plan and task coordination for cross-session projects relies on hydrating Claude Tasks from plan milestones. This enables parallel work and resilience while maintaining progress visibility across documentation.

What is the best way to manage project documentation and status synchronization?

Project documentation and status synchronization are managed through a framework of plan files, phase files, and a references library. This ensures triggers keep teams aligned and records auditable.

Do I need YAML frontmatter in plan files for project tracking?

Yes, YAML frontmatter is required in plan and phase files for project tracking. This structured metadata enables the hydration workflow, progress tracking, and cross-system synchronization via the CLI-based Task tool.

Can I use CLI-based task tools for cross-system synchronization in project management?

Yes, a CLI-based Task tool supports cross-system synchronization in project management. It coordinates tasks hydrated from plan milestones, ensuring progress visibility and documentation alignment across multi-phase projects.

When should I not use plan files for project coordination?

Plan files for project coordination are not ideal for single-session or ad-hoc tasks lacking multi-phase structure. They require YAML frontmatter and a hydration workflow, suited for persistent cross-session planning rather than quick operations.