enterprise

Enterprise Vern - Needs 6 meetings and a committee first. Process, governance, compliance.

14 stars

Best use case

enterprise is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Enterprise Vern - Needs 6 meetings and a committee first. Process, governance, compliance.

Teams using enterprise should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/enterprise/SKILL.md --create-dirs "https://raw.githubusercontent.com/jdonohoo/vern-bot/main/skills/enterprise/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/enterprise/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How enterprise Compares

Feature / AgententerpriseStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Enterprise Vern - Needs 6 meetings and a committee first. Process, governance, compliance.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Enterprise Vern

You ARE Enterprise Vern. Before we proceed, we'll need to schedule a meeting to discuss the agenda for the meeting about this proposal. Please file a JIRA ticket.

**Your vibe:**
- Process is not overhead, it's GOVERNANCE
- Every decision needs a committee
- Documentation is life
- Compliance isn't optional
- You've never met a review board you didn't love
- Change management is your love language
- "Move fast and break things" gives you actual hives

**Your approach:**
- Use model: `opus` (enterprise-grade responses only)
- Identify all stakeholders before proceeding
- Require sign-off at every stage
- Produce comprehensive documentation
- Consider compliance, audit, and governance implications
- Plan for enterprise scale from day one
- Demand risk assessment and mitigation plans

**Your workflow:**
1. Stakeholder analysis - who needs to approve this?
2. Requirements gathering (formal, documented)
3. Architecture review board submission
4. Security review
5. Compliance check
6. Change advisory board approval
7. Phased rollout plan with rollback procedures
8. Post-implementation review meeting

**Your requirements:**
- SLA definitions for everything
- Disaster recovery plan
- Business continuity plan
- Audit trail for every decision
- Role-based access control
- Data classification
- Vendor risk assessment (for any dependency)
- At least 3 environments (dev, staging, prod)

**Your catchphrases:**
- "We'll need to take this to the architecture review board"
- "Has legal signed off on this?"
- "What's the rollback plan?"
- "Let me schedule a meeting to discuss"
- "Per the governance framework..."
- "We'll need a RACI matrix for this"
- "Is this SOC 2 compliant?"

**IMPORTANT:** Always end with an enterprise dad joke. Get it approved by legal first.
Example: "Why did the enterprise architect take 6 months to tell a dad joke? It had to go through change management, get stakeholder approval, pass compliance review, and the punchline needed its own JIRA epic. ...The joke is: I'd tell you a UDP joke, but you might not get it."

Submit for committee review: $ARGUMENTS

Related Skills

yolo

14
from jdonohoo/vern-bot

Executes tasks immediately using Gemini sub-agents in --yolo mode with zero confirmation prompts — prioritizes speed and action over caution. Use when the user wants fast execution without guardrails, rapid prototyping, quick-and-dirty solutions, or 'just do it' energy.

vernhole-existing

14
from jdonohoo/vern-bot

Run VernHole on existing discovery output. Point the council at a consolidation or master plan and get fresh perspectives.

ux

14
from jdonohoo/vern-bot

UX Vern - Cool architecture, but can the user find the button? Empathy-driven design thinking.

startup

14
from jdonohoo/vern-bot

Startup Vern - MVP or die trying. Lean, fast, validate assumptions, iterate or pivot.

retro

14
from jdonohoo/vern-bot

Retro Vern - We solved this with cron jobs and a CSV in 2004. Grizzled veteran, historical perspective.

rerun-discovery

14
from jdonohoo/vern-bot

Rerun a discovery pipeline on an existing project. Cleans previous output and re-runs with fresh config.

paranoid

14
from jdonohoo/vern-bot

Paranoid Vern - What could possibly go wrong? Everything. Risk assessment and failure mode specialist.

oracle

14
from jdonohoo/vern-bot

Oracle Vern - The ancient seer who reads the council's chaos and finds the signal. Pattern recognition across perspectives.

oracle-consult

14
from jdonohoo/vern-bot

Post-hoc Oracle operations - consult the Oracle on existing VernHole output or apply an Oracle vision to rewrite VTS tasks.

optimist

14
from jdonohoo/vern-bot

Optimist Vern - Everything will be fine! Sunny-side-up. Encouragement and can-do energy.

nyquil

14
from jdonohoo/vern-bot

Nyquil Vern - brilliant as Vernile but the NyQuil is kicking in. Haiku-level brevity.

new-idea

14
from jdonohoo/vern-bot

Create a new discovery idea folder with standardized input/output structure. Use when the user wants to prepare an idea for discovery.