ck:plan

Plan software implementations and generate technical roadmaps with phase files.

Updated Apr 2, 2026

Search Tags:#architecture #research #validation #roadmap #plan #red-team #task-hydration

Ready to run

npx skills add https://github.com/hidonguyen/trade-ops --skill ck-plan-hidonguyen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ck:plan
Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/ck-plan
Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-plan-hidonguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Breaks ambiguous feature requests into actionable, well-scoped implementation plans and roadmaps so teams can execute reliably without repeated scope churn or missing dependencies.

Core Features & Use Cases

Cross-plan dependency detection: scans unfinished plans and updates blockedBy/blocks relationships to prevent hidden blockers.
Structured planning workflow: guides scope challenge, research, codebase analysis, solution design, phase creation, hydration, red-team review, and validation.
Use Case: Turn a feature brief into a plan directory with plan.md, phase files, research reports, and hydrated tasks ready for handoff to implementation.

Quick Start

Run the plan skill with a concise task description, for example: /ck:plan "Add OAuth2 login --hard"

Frequently Asked Questions about ck:plan

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

FAQPage Schema

How do I break down an ambiguous feature request into an actionable implementation plan?▼

To create an implementation plan, you can use structured planning workflows that break ambiguous feature requests into scoped phases, research reports, and hydrated tasks. This produces a plan.md file and phase files ready for execution.

What is cross-plan dependency resolution and how does it prevent hidden blockers?▼

Cross-plan dependency resolution scans unfinished plans to detect and update blockedBy/blocks relationships. This mechanism prevents hidden blockers by mapping dependencies between concurrent technical roadmaps before execution begins.

How do I structure technical roadmaps for complex system architecture designs?▼

Structuring technical roadmaps involves applying a workflow of scope challenge, codebase analysis, solution design, and phase creation. This systematically translates system architecture designs into hydrated task lists for reliable execution.

Can I include red-team review and validation steps in my feature planning workflow?▼

Yes, feature planning workflows can include red-team review and validation steps. Applying adversarial review to solution design and phase creation helps identify weaknesses in technical implementation strategies before handoff.

What is task hydration in the context of software implementation planning?▼

Task hydration is the process of expanding structured plan phases into detailed, actionable tasks. It occurs after solution design and phase creation, generating the granular implementation details needed for developer handoff.

Does this planning workflow support scanning existing plans in a repository?▼

Yes, the planning workflow supports repository scans of existing plans. Scanning existing plan directories allows the system to resolve cross-plan dependencies and update blocked relationships across unfinished features.