ck:plan

Generate phase-based implementation plans with cross-plan dependencies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning, architecture, and roadmapping for software projects, enabling structured plans with phases and milestones.

Core Features & Use Cases

  • Create detailed implementation plans with research, design, and documentation
  • Generate phase-based plan files and cross-plan dependencies
  • Align planning with governance and execution workflows

Quick Start

Create a new plan under plans/ with a plan.md and phase-01 to phase-03 files.

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 phased implementation plan for a complex software project?

A cross-plan dependency is a structural link between separate implementation plans. You manage cross-plan dependencies by enforcing pre-creation checks and workflow options to align planning with governance and execution workflows.

What's the best way to structure roadmaps and architecture documentation?

The best way to structure roadmaps and architecture documentation is by generating phase-based plan files, such as a main plan file alongside phase-01 to phase-03 files, to ensure clear phased delivery and milestone tracking.

Can I align project planning with governance and execution workflows?

Yes, you can align project planning with governance and execution workflows. The planning process enforces pre-creation checks and provides workflow options to guide planning activities and ensure structured delivery.

Do I need to define dependencies before designing software architecture plans?

Yes, you need to define dependencies before designing software architecture plans. The planning mechanism analyzes requirements, references, and dependencies to generate actionable plans and enforce cross-plan dependency checks.