ck:plan

Generate detailed technical implementation plans as structured markdown with phases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often struggle to create thorough technical implementation plans, leading to missed requirements, security gaps, and delayed deliveries.

Core Features & Use Cases

  • Research & Analysis: Automatic discovery of relevant code, documentation, and external resources.
  • Solution Design: Structured architecture and trade‑off evaluation with YAGNI, KISS, and DRY principles.
  • Red Team Review: Adversarial assessment to surface hidden risks and flaws.
  • Validation Interview: Targeted questions that confirm assumptions and expose trade‑offs.
  • Task Hydration: Generates persistent plan files and session‑scoped Claude tasks for seamless handoff to the cook.

Use Cases

  • Planning a new multi‑tenant feature in a SaaS product.
  • Designing a system‑wide architecture overhaul.
  • Creating a phased roadmap for complex integrations.

Quick Start

Ask me to create a plan for a feature by saying, “Create a plan for adding role‑based access control to the API.”

Frequently Asked Questions about ck:plan

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

FAQPage Schema
How do I generate a technical implementation plan for a software feature?

To generate a technical implementation plan, define your feature or system redesign scenario. The skill produces structured markdown covering research, design, validation, and phased task hydration for seamless development handoff.

What is red team review in software architecture design?

Red team review is an adversarial assessment applied during architecture design to surface hidden risks and flaws. It evaluates trade-offs using YAGNI, KISS, and DRY principles to validate the proposed system roadmap.

Can I use this to create a roadmap for a multi-tenant SaaS integration?

Yes, you can create a phased roadmap for complex integrations like multi-tenant SaaS features. The skill automatically discovers relevant code and documentation to structure the architecture and validate assumptions.

How do I validate assumptions and expose trade-offs before system redesign?

You validate assumptions through a targeted validation interview that confirms requirements and exposes trade-offs. The skill generates targeted questions alongside the architecture design to ensure system redesign accuracy.

What is the best way to structure an architecture roadmap with task hydration?

The best way to structure an architecture roadmap is using phased markdown with research, design, and validation sections. Task hydration generates persistent plan files and session-scoped tasks for immediate development execution.

Do I need external dependencies to evaluate architecture trade-offs?

No external dependencies are required to evaluate architecture trade-offs. The skill applies YAGNI, KISS, and DRY principles internally to assess solution design and generate the implementation roadmap independently.