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

ck:predict

Analyze proposed software changes for architectural, security, performance, UX, and strategic risks.

Updated May 10, 2026
Search Tags:#architecture#code review#performance#security#design review#ux#risk analysis
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-predict-dthuy62
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:predict
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/ck-predict
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-predict-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk of building the wrong thing by pressure-testing a proposed change before implementation begins, surfacing architectural, security, performance, UX, and strategy concerns early.

Core Features & Use Cases

  • Multi-perspective analysis: Five independent personas review the proposal from different angles to expose blind spots.
  • Conflict resolution: The skill compares disagreements, weighs tradeoffs, and turns them into a clear go, caution, or stop verdict.
  • Risk-focused planning: It is useful for major features, risky refactors, competing technical approaches, and other decisions that benefit from early scrutiny.

Quick Start

Ask the ck:predict skill to evaluate your proposed change and include any relevant file paths so it can produce a verdict and actionable recommendations.

Frequently Asked Questions about ck:predict

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

FAQPage Schema
How do I analyze architectural and security risks before implementing a major feature?▼

Pre-implementation risk analysis evaluates proposed software changes across five independent expert personas, surfacing architectural, security, performance, UX, and strategic concerns. It compares tradeoffs and resolves conflicts to produce a clear go, caution, or stop verdict.

What is the best way to pressure-test a risky code refactor before writing any code?▼

Pressure-testing a risky code refactor involves applying multi-perspective scrutiny to the proposal before development begins. Five expert personas review the design independently to expose blind spots and deliver actionable recommendations for early risk-focused planning.

Can I evaluate competing technical design alternatives for high-stakes development decisions?▼

Yes, you can evaluate competing technical design alternatives by submitting the approaches for independent persona review. The analysis weighs architectural, security, performance, and UX tradeoffs to resolve disagreements and output a final verdict.

How do I get a go, caution, or stop verdict for a proposed software change?▼

To get a go, caution, or stop verdict, submit your proposed change along with relevant file paths for evaluation. The independent persona reviews identify architectural and security risks, compare disagreements, and turn the tradeoffs into an actionable verdict.

When do I need a preflight design review for UX and performance risks?▼

A preflight design review is needed for major features, risky refactors, and competing technical approaches where high stakes demand early scrutiny. It surfaces UX and performance concerns before implementation begins to reduce the risk of building the wrong thing.

Related Skills

Explore More Software Engineering Skills→
tranvietanh0tranvietanh0

t1k:predict

Debate proposed software changes across architectural, security, performance, and UX domains.

Community
Advanced
misfitdevmisfitdev
2

hold-my-beer

Generate a 9-section execution plan with rollback steps and a GO/NO-GO verdict.

Official
Advanced
adolfoaranaes12adolfoaranaes12
2

risk-profile

Score implementation risks by Probability × Impact across six categories.

Community
Advanced
zangjeicyzangjeicy

requesting-code-review

Scan git diffs for security vulnerabilities and quality regressions.

Community
Advanced