ck:plan

Manage software project plans with YAML frontmatter, phases, and validation workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan and govern complex feature planning tasks, architecture design, and roadmapping with standardized workflows including pre-creation checks, mode detection, red-team and validation gates.

Core Features & Use Cases

  • Centralized planning with plan.md and phase files
  • Cross-plan dependency detection and automatic updates
  • Pre-creation checks, scope challenge, and mode detection
  • Red-team review and validation workflows
  • Task hydration and journaling integration
  • Active Plan State tracking and context reminders
  • Reference materials in planning references for consistency

Quick Start

Create a new CK plan for the authentication module by filling plan.md and phase files with phases and tasks.

Frequently Asked Questions about ck:plan

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

FAQPage Schema
How do I manage software project plans with cross-plan dependencies and validation gates?

Manage software project plans by using centralized plan.md and phase files to structure tasks, detect cross-plan dependencies, and enforce red-team reviews with validation gates. This ensures coordinated execution and strict development-rule conformance across teams.

What is the best way to structure a roadmap for a complex system redesign across multiple teams?

The best way to structure a roadmap for a complex system redesign is to apply centralized planning with YAML frontmatter-driven plan files, phase templates, and task hydration to coordinate teams and document implementation.

How does red-team review and pre-creation scope challenge work in feature planning?

Red-team review and pre-creation scope challenge work by applying validation workflows and mode detection before plan creation, actively challenging the scope to ensure feature rollout plans are robust and conform to development rules.

Can I use YAML frontmatter and phase templates for feature rollout planning?

Yes, you can use YAML frontmatter and phase templates for feature rollout planning to drive plan files, hydrate tasks, and integrate journaling. This standardizes workflows and maintains active plan state tracking across teams.

What are the limitations of relying on plan.md files for architecture governance?

Limitations of relying on plan.md files include the need for strict pre-creation checks and dependency management to prevent state drift. Without active context reminders and journaling integration, architecture governance across teams may lose validation consistency.