skills.rest
dthuy62
dthuy62COMMUNITY
Explore all skills by this author →
GitHub

ck:plan

Create detailed technical implementation plans with phases and dependency tracking.

Updated May 10, 2026
Search Tags:#planning#architecture#codebase#validation#implementation#dependencies#roadmap
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-plan-dthuy62
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:plan
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/ck-plan
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-plan-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns vague software requests into structured implementation plans, so teams can move from idea to execution with less confusion, rework, and scope drift.

Core Features & Use Cases

  • Technical Roadmapping: Break features, refactors, and platform work into phased delivery plans.
  • Architecture and Trade-off Analysis: Compare solution options, identify dependencies, and design maintainable approaches.
  • Plan Quality Workflow: Run scope checks, research, red-team review, validation, and task hydration before implementation.
  • Use Case: A product engineer can use this Skill to convert a feature request into a detailed, dependency-aware rollout plan with risks, milestones, and next steps.

Quick Start

Ask the skill to create a detailed implementation plan for your feature, including phases, dependencies, risks, and validation steps.

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 implementation plan for a complex software feature?▼

Create a technical implementation plan by breaking software work into structured phases, tracking cross-plan dependencies, and documenting execution strategy, risks, and validation steps for reliable delivery.

What is the best way to structure a refactoring roadmap for an existing codebase?▼

Structure a refactoring roadmap by applying scope control, cross-plan dependency detection, and phased documentation across the codebase to sequence tasks, mitigate risks, and guide maintainable architecture transitions.

How do I run an architecture trade-off analysis before starting implementation?▼

Run an architecture trade-off analysis by comparing solution options, identifying technical dependencies, and conducting validation interviews and red-team reviews to design a maintainable approach before coding begins.

Can I use task hydration to convert a high-level software plan into actionable steps?▼

Yes, task hydration expands high-level roadmap phases into detailed, actionable execution steps, ensuring every task includes necessary scope checks, validation requirements, and dependency context for reliable delivery.

When should I not use a phased delivery plan for software work?▼

Avoid phased delivery plans for trivial, single-file changes that lack cross-plan dependencies, or when scope drift and architecture validation are not concerns, as the overhead adds unnecessary friction.

Related Skills

Explore More Software Engineering Skills→
arroyo2009jose-maxarroyo2009jose-max

prp

Generate a PRP with objective, behavior, data model, and phased milestones.

Community
Advanced
kerolos-saaidkerolos-saaid

speckit-implement

Execute phased TDD development workflows from tasks.md and plan.md.

Community
Advanced
kaptinlinkaptinlin
23

architecture-audit

Audit Go codebases for circular dependencies, fat interfaces, and spec drift.

Community
Advanced
CaptainCrouton89CaptainCrouton89
497

Planning Implementation

Create structured implementation plans with tasks, dependencies, and risks.

Community
Basic