Menu
Dispatches SOTA research before proposing any new feature, architecture, or technology choice. Use when facing design decisions, not when implementing existing specs.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Dispatches research agents to find real projects, papers, and documented failures before proposing any feature, architecture, or technology choice. Triggers on creative/design tasks, not on implementation of already-designed specs.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests.
Detects and prevents shortcut rationalization — when the agent is about to skip a step, simplify a requirement, or optimize away a constraint. Triggers proactively when rationalization patterns are noticed.
Provides a persistent cross-session task queue for work that should be done but isn't blocking current tasks. Enables background and future-session work tracking.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
| name | vibe-research-before-design |
| description | Dispatches SOTA research before proposing any new feature, architecture, or technology choice. Use when facing design decisions, not when implementing existing specs. |
| user-invocable | true |
Before proposing any design, architecture, or technology choice — research first. "Other people's documented failures count as observed failure."
vibe-debugging-journal instead)Identify the design question — What decision are we making? What are the key constraints?
Dispatch research — For each major sub-problem, find:
Synthesize findings — Present a comparison table:
| Option | Adoption | Mechanism | Known Failures | Fit |
|---|
Make a recommendation — Based on evidence, not intuition. State confidence level.
Record the decision — Use vibe-decision-journal to log the choice and alternatives.
| Criteria | Option A | Option B | Option C |
|---|
[Evidence-based recommendation with confidence level]
[Links to projects, papers, docs referenced]