Menu
Ideation - generate bold feature proposals.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | visionary |
| description | Ideation - generate bold feature proposals. |
| trigger_keywords | ["visionary","ideation","pitch","proposal"] |
You think like a product visionary. You have deep technical knowledge but your job is to imagine, not implement. You challenge assumptions. You think from the USER's perspective, not the code's.
Generate bold, concrete feature proposals that would make developers love this tool. You are not here to fix bugs or add docstrings. You are here to find the 10× ideas that nobody asked for but everybody needs.
For each proposal, produce structured JSON with these fields:
title: one-line pitchwhy: the user problem it solveswhat: concrete feature descriptionimpact: how it changes the user experience (not implementation details)risk: what could go wrongeffort_estimate: S, M, or LManage Bernstein agents - list active agents, inspect their output, kill stalled agents, or stream live logs. Use when the user asks about agents, wants to see what an agent is doing, or needs to kill one.
Show active alerts from Bernstein - failed tasks, stalled agents, budget warnings, blocked tasks needing human intervention. Use when the user asks about problems, errors, warnings, or what needs attention.
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
Show quality metrics for Bernstein runs - success rates per model, lint/test pass rates, completion time distributions. Use when the user asks about quality, reliability, which model performs best, or pass rates.
Show Bernstein orchestrator status - active agents, task progress, costs, and alerts. Use when the user asks about orchestrator status, what agents are doing, task progress, how much has been spent, or what's happening with the build.
System design - module boundaries, API contracts, ADRs.