ck:plan

Plan technical implementations and roadmaps for software projects.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-plan-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:plan
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/ck-plan
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-plan-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a disciplined, reproducible workflow for planning technical implementations, system architecture, and phased roadmaps so teams avoid scope drift, missed dependencies, and unclear handoffs.

Core Features & Use Cases

  • Cross-plan dependency detection: scans existing plans in ./plans/, reads plan.md frontmatter, and marks blockedBy/blocks relationships to prevent conflicting work.
  • Structured plan generation: produces plan.md and phase-XX.md files following strict frontmatter and output standards with task-hydration guidance.
  • Review pipelines: supports archive, adversarial red-team reviews, and validation interviews to harden plans before implementation.
  • Operational safety: prompts for confirmations on destructive actions (archive/delete) and mandates ask-user checkpoints for ambiguous decisions.

Quick Start

Use the ck:plan skill to create a new implementation plan for adding OAuth2 authentication, scanning ./plans/ for blockers and outputting the plan directory path.

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 technical roadmap that detects dependencies across existing plans?

To create a technical roadmap with dependency detection, scan the ./plans/ directory to read plan.md frontmatter and update blockedBy/blocks relationships, ensuring no conflicting work or missed dependencies across features.

What is cross-plan dependency detection in software architecture planning?

Cross-plan dependency detection reads plan.md frontmatter in ./plans/ to map blockedBy/blocks relationships, identifying conflicting work and scope drift before implementation begins.

How do I structure a phased implementation plan for a new software feature?

Structure a phased implementation plan by scaffolding plan.md and phase-XX.md files following strict frontmatter standards, then output cook commands and task-hydration instructions to guide execution.

Can I perform a red-team review on my solution architecture plan before implementation?

Yes, you can perform adversarial red-team reviews and validation interviews to harden your solution architecture plan, identifying weaknesses and verifying completeness before starting the actual implementation phase.

Does this planning workflow require any external dependencies or frameworks?

No external dependencies or frameworks are required, as the workflow operates by scanning local ./plans/ directories and generating standard markdown files with frontmatter for task hydration.

What happens to archived technical plans during a repository cleanup?

Archived technical plans undergo archival workflows that prompt for confirmation on destructive actions like deletion, ensuring operational safety and preventing accidental loss of plan history.