ck:predict

Analyze proposed technical changes with five expert personas and output a GO/CAUTION/STOP verdict.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/quanganh208/cookmate --skill ck-predict-quanganh208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:predict
Source: https://github.com/quanganh208/cookmate/tree/main/.opencode/skills/ck-predict
Command: npx skills add https://github.com/quanganh208/cookmate --skill ck-predict-quanganh208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill catches architectural, security, performance, UX, and hidden-assumption risks before implementation by running a structured, multi-persona debate to produce a clear GO / CAUTION / STOP verdict and actionable mitigations.

Core Features & Use Cases

  • Five independent expert analyses: Architect, Security, Performance, UX, and Devil's Advocate each evaluate the proposal without influencing one another.
  • Structured debate protocol: Identifies agreements, conflicts, tradeoffs, and produces a consensus verdict with prioritized recommendations and risk mitigations.
  • Use Cases: Evaluate major new features, large refactors, API or auth changes, and risky technology swaps before a single line of code is written.

Quick Start

Run the skill by sending a concise feature description such as: /ck:predict Add WebSocket support for real-time notifications and optionally include --files to reference affected code paths.

Frequently Asked Questions about ck:predict

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

FAQPage Schema
How do I catch architecture and security risks before implementation?

To catch architecture and security risks before implementation, analyze proposed technical changes using five expert personas to evaluate the proposal independently and surface a consensus GO/CAUTION/STOP verdict with mitigations.

What is a multi-persona risk analysis for pre-implementation review?

A multi-persona risk analysis for pre-implementation review evaluates proposed changes through Architect, Security, Performance, UX, and Devil's Advocate personas independently to identify agreements, conflicts, and tradeoffs before producing a final consensus verdict.

How do I evaluate a large refactor for UX and performance risks?

To evaluate a large refactor for UX and performance risks, submit a concise feature description with optional file globs to trigger independent persona evaluations that weigh tradeoffs and output concrete recommendations for your architectural changes.

Does pre-implementation risk analysis work for API and auth changes?

Pre-implementation risk analysis works for API and auth changes by running a structured debate protocol across five expert personas to surface security, performance, and assumption risks before a single line of code is written.

Can I use a structured debate protocol for risky technology swaps?

You can use a structured debate protocol for risky technology swaps to identify conflicts and tradeoffs across architecture, security, performance, and UX dimensions, producing a clear GO/CAUTION/STOP verdict with prioritized recommendations.