ck:plan

Generate structured project plans with phases, tasks, and design decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex software projects requires structured instructions, traceable roadmaps, and clear phase definitions to align teams and manage risks.

Core Features & Use Cases

  • Formal plan creation for feature planning, system design, and implementation roadmaps.
  • Phase-based execution guidance with dependencies, risks, and acceptance criteria.
  • Collaborative review workflows including red-team and validation steps.

Quick Start

Outline a plan by listing phases, dependencies, and risk considerations for a given task.

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 project roadmap with phase dependencies and risk management?

A project roadmap requires a self-contained plan consisting of phases, tasks, and design decisions. It proposes dependencies, risks, and acceptance criteria for each phase to ensure structured execution.

What is phase-based execution guidance for software architecture planning?

Phase-based execution guidance breaks architecture planning into structured phases with defined dependencies, risks, and acceptance criteria. It maps to actionable plan files ready for hydration and review.

How do I enforce scope challenge and red-team review workflows during feature planning?

Enforcing scope challenge and red-team review workflows involves applying the project's development rules during planning. This validation process ensures robust, maintainable outcomes before execution.

Can I use this planning approach for complex system design and requirements traceability?

Yes, this approach supports complex system design and requirements traceability by analyzing project context and generating formal plans. It provides clear phase definitions to align teams and manage risks.

What are the limitations of relying on self-contained plan files for collaboration?

Self-contained plan files require manual hydration and collaborative review to remain effective. Without enforcing red-team and validation workflows, the generated phase definitions may not fully mitigate project risks.