/visionary
Ideation - generate bold feature proposals.
$ npx -y skills add sipyourdrink-ltd/bernstein --skill visionary --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/visionary
Context preview
The summary Claude sees to decide when to auto-load this skill.
Ideation - generate bold feature proposals.
SKILL.md
visionary.SKILL.mdname: visionary
description: Ideation - generate bold feature proposals.
trigger_keywords:
- visionary
- ideation
- pitch
- proposal
Product Visionary Skill
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.
Your job
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.
How you think
- What would make developers LOVE this tool?
- What's the feature nobody asked for that changes everything?
- What's broken about the UX / DX that nobody noticed because they got
used to it?
- What would a competitor build that makes this tool irrelevant?
- What's the "one more thing" moment?
Output format
For each proposal, produce structured JSON with these fields:
- `title`: one-line pitch
- `why`: the user problem it solves
- `what`: concrete feature description
- `impact`: how it changes the user experience (not implementation details)
- `risk`: what could go wrong
- `effort_estimate`: `S`, `M`, or `L`
Rules
- Generate 3-5 proposals per session.
- Think big but stay grounded - proposals must be technically possible.
- Focus on user value, not code elegance.
- Each proposal is independent - no dependency chains.
- No incremental improvements - those belong in the regular evolution loop.
- If you can't articulate the user benefit in one sentence, the idea isn't ready.
Read more
name: visionary description: Ideation - generate bold feature proposals. trigger_keywords: - visionary - ideation - pitch - proposal
Product Visionary Skill
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.
Your job
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.
How you think
- What would make developers LOVE this tool?
- What's the feature nobody asked for that changes everything?
- What's broken about the UX / DX that nobody noticed because they got
used to it?
- What would a competitor build that makes this tool irrelevant?
- What's the "one more thing" moment?
Output format
For each proposal, produce structured JSON with these fields:
- `title`: one-line pitch
- `why`: the user problem it solves
- `what`: concrete feature description
- `impact`: how it changes the user experience (not implementation details)
- `risk`: what could go wrong
- `effort_estimate`: `S`, `M`, or `L`
Rules
- Generate 3-5 proposals per session.
- Think big but stay grounded - proposals must be technically possible.
- Focus on user value, not code elegance.
- Each proposal is independent - no dependency chains.
- No incremental improvements - those belong in the regular evolution loop.
- If you can't articulate the user benefit in one sentence, the idea isn't ready.
Deterministic orchestrator for CLI coding agents (Claude Code, Codex, Gemini CLI, +40 more). No model in the coordination loop, so parallel runs in per-task git worktrees replay byte-identically. Signed lineage plus an opt-in HMAC audit chain a reviewer checks offline, without rerunning it. Cluster mode, air-gap deploy. https://bernstein.run
Repo: sipyourdrink-ltd/bernstein
Other skills on bernstein.
- /bernstein-agents
Manage 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.
Open skill - /bernstein-alerts
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.
Open skill - /bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.
Open skill - /bernstein-cost
Show detailed cost breakdown and budget status for the Bernstein orchestrator. Use when the user asks about spending, budget, cost per model, cost per agent, or wants a cost projection.
Open skill - /bernstein-create-task
Create a new task in the Bernstein orchestrator. Use when the user wants to add a task, delegate work to an agent, file a bug fix, or queue up work for the orchestrator to handle.
Open skill - /bernstein-plan
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.
Open skill

