ck:plan

Generate structured plan.md files with phases and dependencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning and governance for complex product work: it creates structured plans that capture scope, architecture, phases, and cross-team dependencies.

Core Features & Use Cases

  • Generate a complete plan.md with phase-01.md, phase-02.md, etc., including frontmatter and dependencies
  • Enable adversarial review and validation workflows to ensure plan quality before execution
  • Hydrate tasks and coordinate with the cook handoff in preparation for implementation

Quick Start

Run the planner for a new task, provide a plan title and directory, then fill the generated plan with phases and details.

Frequently Asked Questions about ck:plan

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

FAQPage Schema
How do I create a structured roadmap with phased implementation and cross-team dependencies?▼

To create a structured roadmap with phased implementation, you generate a plan with phase-based files, frontmatter, and defined dependencies. This enforces scoping rules and validation steps to ensure executable cross-team coordination.

What is feature planning governance and how does it handle task hydration?▼

Feature planning governance orchestrates implementations by enforcing scoping rules and mode selection before execution. Task hydration translates validated phases into downstream actionable items, ensuring structured handoffs for implementation.

How do I validate architecture plans before execution using an adversarial review?▼

You validate architecture plans before execution by applying an adversarial red-team review during the generation process. This enforces scoping rules and validation workflows to ensure plan quality and scope accuracy.

Can I use this to plan system architectures for complex product work across multiple teams?▼

Yes, you can use this to plan system architectures for complex product work. It generates structured guidance for cross-team planning, capturing scope, architecture, phases, and dependencies to orchestrate implementations.

What is the best way to generate phase-based plan files with frontmatter for development workflows?▼

The best way to generate phase-based plan files with frontmatter is to run the planner with a title and directory. It creates a complete plan structure with sequential phase files and dependency mapping for execution.

Are there limitations when enforcing scoping rules for large feature implementations?▼

Scoping limitations arise if complex feature implementations bypass the enforced mode selection and red-team review. Proper governance requires strict adherence to validation steps to ensure downstream task hydration remains executable.