OpenParable
Skip to content
← Back to skills

ck:predict

Testing & Quality

ck:predict is an Agent Skill for testing & quality published in the phuc-nt/my-translator repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

5 expert personas debate proposed changes before implementation. Catches architectural, security, performance, and UX issues early. Use before major features or risky changes.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/phuc-nt/my-translator/blob/HEAD/.opencode/skills/ck-predict/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ck-predict, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

ck:predict — Multi-Persona Pre-Analysis

Five expert personas independently analyze a proposed change, then debate conflicts to produce a consensus verdict before a single line of code is written.

When to Use

  • Before implementing a major or high-risk feature
  • Before a significant refactor or architecture change
  • Evaluating competing technical approaches
  • Stress-testing assumptions in a proposed design

When NOT to Use

  • Trivial or low-risk changes (use ck:debug for bugs, ck:plan for already-decided tasks)
  • Already-approved work with no open design questions
  • Pure dependency upgrades with no API changes

The 5 Personas

PersonaFocusCore Questions
ArchitectSystem design, scalability, couplingDoes this fit the architecture? Will it scale? What new coupling does it introduce?
SecurityAttack surface, data protection, authWhat can be abused? Where is data exposed? Are auth boundaries respected?
PerformanceLatency, memory, queries, bundle sizeWhat is the latency impact? N+1 queries? Memory leaks? Bundle bloat?
UXUser experience, accessibility, error statesIs this intuitive? What does the error state look like? Accessible on mobile?
Devil's AdvocateHidden assumptions, simpler alternativesWhy not do nothing? What is the simplest alternative? Which assumption could be wrong?

Debate Protocol

  1. Read the proposed change/feature description from the argument
  2. Read relevant code if file paths are provided (grep for affected areas)
  3. Each persona analyzes independently — do not let personas influence each other during this phase
  4. Identify agreements — points where all (or 4+) personas align
  5. Identify conflicts — points where personas meaningfully disagree
  6. Weigh tradeoffs — for each conflict, evaluate which concern has higher impact
  7. Produce verdict — GO / CAUTION / STOP with actionable recommendations

Output Format

## Prediction Report: [proposal title]

## Verdict: GO | CAUTION | STOP

### Agreements (all personas align)
- [Point 1 — what they all agree on]
- [Point 2]

### Conflicts & Resolutions

| Topic | Architect | Security | Performance | UX | Devil's Advocate | Resolution |
|-------|-----------|----------|-------------|-----|-----------------|------------|
| [Issue] | [View] | [View] | [View] | [View] | [View] | [Recommendation] |

### Risk Summary

| Risk | Severity | Mitigation |
|------|----------|------------|
| [Risk description] | Critical/High/Medium/Low | [Concrete action] |

### Recommendations
1. [Action item — rationale]
2. [Action item — rationale]
3. [Action item — rationale]

Verdict Levels

VerdictMeaning
GOAll personas aligned, no critical risks, proceed with confidence
CAUTIONConcerns exist but are manageable — mitigations identified, proceed carefully
STOPCritical unresolved issue found — needs redesign or more information before proceeding

STOP Triggers (any one is sufficient)

  • Security persona identifies auth bypass or data exposure with no viable mitigation
  • Architect identifies fundamental design incompatibility requiring significant rework
  • Performance persona identifies unacceptable latency or query explosion with no workaround
  • Devil's Advocate exposes a false assumption that invalidates the entire approach

Integration with Other Skills

Workflow StepSkillHow
Deepen risk scenariosck:scenarioFeed Risk Summary rows as feature description
Create implementation planck:planAttach Recommendations as constraints to planner
High-risk feature implementationck:cookReference CAUTION/STOP items as acceptance gates

Example Invocations

/ck:predict "Add WebSocket support for real-time notifications"
/ck:predict "Migrate authentication from JWT to session cookies"
/ck:predict "Add multi-tenancy to the database layer"
/ck:predict "Replace REST API with GraphQL" --files src/api/**/*.ts