ワンクリックでManusで任意のスキルを実行

omg-predict

スター1

フォーク0

更新日2026年5月26日 19:10

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

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

tranvietanh0

tranvietanh0/oh-my-game-kit

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Codex Port Notice

This skill was ported from upstream reference material. Interpret command names, paths, and agent-routing guidance as Codex/Oh My Game Kit equivalents. Prefer active Codex tools and local project instructions over Codex-specific mechanics when they conflict.

Oh My Game Kit Predict — Expert Debate

5 expert personas review a proposed change and debate its merits, risks, and alternatives.

Usage

omg-predict "Add caching layer to API responses"

Personas

#	Persona	Focus	Looks For
1	Architect	System design, scalability, coupling	Over-engineering, tight coupling, wrong abstractions, missing extensibility
2	Security	Attack surface, data flow, trust boundaries	Auth bypass, injection, data exposure, insufficient logging
3	Performance	Bottlenecks, memory, latency	N+1 queries, unnecessary allocations, cache invalidation issues
4	UX/DX	User/developer impact, edge cases	Breaking changes, poor error messages, confusing APIs
5	Devil's Advocate	Assumptions, alternatives, hidden costs	"What if this is the wrong approach entirely?"

Process

Read the proposed change description
Each persona reviews independently:
- State their concerns (1-3 bullet points)
- Rate risk for their domain (1-5 scale)
- Suggest mitigations
Synthesize:
- Consensus risk score (average of 5 ratings)
- Prioritized concern list (highest risk first)
- Go/No-Go recommendation with conditions

Output Format

## Prediction: {change description}

### Architect (Risk: 3/5)
- Concern: ...
- Mitigation: ...

### Security (Risk: 2/5)
- Concern: ...
- Mitigation: ...

### Performance (Risk: 4/5)
- Concern: ...
- Mitigation: ...

### UX/DX (Risk: 1/5)
- Concern: ...
- Mitigation: ...

### Devil's Advocate (Risk: 3/5)
- Alternative: ...
- Hidden cost: ...

### Consensus
- **Overall Risk: 2.6/5**
- **Recommendation: GO with conditions**
- **Top 3 concerns to address:**
  1. ...
  2. ...
  3. ...

Anti-Rationalization Guards

Trap	Reality
"This change is too simple for a debate"	Simple changes with hidden complexity cause the worst incidents.
"We already discussed this"	Discussion ≠ structured risk assessment.
"The user wants to start coding"	5 minutes of prediction saves 5 hours of debugging.

When to Use

Before any change affecting >3 files
Before any security-sensitive change
Before any architectural decision
When the team disagrees on approach
When risk feels "medium" or higher

Sub-Agent Fork Hygiene

Sub-agent forking: see .agents/skills/omg-architecture/references/fork-hygiene.md.

このリポジトリの他の Skills

同じリポジトリ

omg-unity-architecture-assembly-graph

tranvietanh0/oh-my-game-kit

Unity engine adapter: .asmdef graph, Roslyn class diagrams with Unity stereotypes (MonoBehaviour, ScriptableObject, DOTS), UPM package deps, and C4 architecture views

2026-05-261

omg-cocos-playable-parameter

tranvietanh0/oh-my-game-kit

Cocos Creator 3.8.7 playable-ad parameter discovery + implementation. Scans project config files (constant.ts, *Config.ts) AND all Canvas UI nodes via MCP, reads scene values for defaults, wires bindings, auto-assigns. Modes: --quick, --standard, --deep, --exhaustive, --auto.

2026-05-261

omg-unity-editor-sync

tranvietanh0/oh-my-game-kit

Compare CK updates against GameKit baseline, suggest which changes to incorporate.

2026-05-261

omg-ask

tranvietanh0/oh-my-game-kit

Answer technical questions with context-aware skill activation. Use for 'how does X work', 'what is the best way to', 'explain this pattern' queries.

2026-05-261

omg-context

tranvietanh0/oh-my-game-kit

Check context usage limits, monitor time remaining, optimize token consumption, debug context failures. Use when asking about context window, token budget, or agent context sizing.

2026-05-261

omg-cook

tranvietanh0/oh-my-game-kit

Implement features end-to-end: plan, code, test, review via registry agents. Use for 'implement X', 'build Y feature', 'add Z functionality'. Handles full workflow.

2026-05-261

Oh My Game Kit Predict — Expert Debate

5 expert personas review a proposed change and debate its merits, risks, and alternatives.

Usage

omg-predict "Add caching layer to API responses"

Personas

Persona

Focus

Looks For

Architect

System design, scalability, coupling

Over-engineering, tight coupling, wrong abstractions, missing extensibility

Security

Attack surface, data flow, trust boundaries

Auth bypass, injection, data exposure, insufficient logging

Performance

Bottlenecks, memory, latency

N+1 queries, unnecessary allocations, cache invalidation issues

UX/DX

User/developer impact, edge cases

Breaking changes, poor error messages, confusing APIs

Devil's Advocate

Assumptions, alternatives, hidden costs

"What if this is the wrong approach entirely?"

Process

Read the proposed change description

Each persona reviews independently:

State their concerns (1-3 bullet points)
Rate risk for their domain (1-5 scale)
Suggest mitigations

Synthesize:

Consensus risk score (average of 5 ratings)
Prioritized concern list (highest risk first)
Go/No-Go recommendation with conditions

Output Format

## Prediction: {change description} ### Architect (Risk: 3/5) - Concern: ... - Mitigation: ... ### Security (Risk: 2/5) - Concern: ... - Mitigation: ... ### Performance (Risk: 4/5) - Concern: ... - Mitigation: ... ### UX/DX (Risk: 1/5) - Concern: ... - Mitigation: ... ### Devil's Advocate (Risk: 3/5) - Alternative: ... - Hidden cost: ... ### Consensus - **Overall Risk: 2.6/5** - **Recommendation: GO with conditions** - **Top 3 concerns to address:** 1. ... 2. ... 3. ...

Anti-Rationalization Guards

Trap

Reality

"This change is too simple for a debate"

Simple changes with hidden complexity cause the worst incidents.

"We already discussed this"

Discussion ≠ structured risk assessment.

"The user wants to start coding"

5 minutes of prediction saves 5 hours of debugging.

When to Use

Before any change affecting >3 files

Before any security-sensitive change

Before any architectural decision

When the team disagrees on approach

When risk feels "medium" or higher

Sub-Agent Fork Hygiene

Sub-agent forking: see .agents/skills/omg-architecture/references/fork-hygiene.md.

name	omg-predict
description	5 expert personas debate proposed changes before implementation. Catches architectural, security, performance, and UX issues early. Use before major features or risky refactors.