Visionary

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 6ba64a7d2489 · 14 Oct 2026Report an issue or request a re-scan

• Publishersipyourdrink-ltd GitHub organizationOwner of the repository this skill is read from
• Source foldersipyourdrink-ltd/bernstein/templates/skills/visionaryThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict6ba64a7d2489A new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Ideation - generate bold feature proposals.

---
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.

Excerpt, first 1,610 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/sipyourdrink-ltd/bernstein
git -C bernstein checkout 6ba64a7d2489

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 6ba64a7d2489

Questions about Visionary

• github.com/sipyourdrink-ltd/bernstein/tree/main/templates/skills — the audited source at commit 6ba64a7d2489 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology