workshop
MANDATORY PREPARATION
Invoke /product-thinking — it contains the Context Gathering Protocol and the AI Slop Test. Follow the protocol before proceeding.
Mindset
A workshop is not brainstorming. Brainstorming produces 40 ideas and zero decisions. A workshop starts from grounded inputs — what users actually do, what competitors actually ship, where value actually flows — and converges on opportunities worth pursuing.
This is a conversation, not a monologue. Push back. Ask "why would someone care?" Challenge assumptions. The best workshops produce two or three sharp ideas, not twenty vague ones.
Context Pull
Load all available intelligence:
- Product context. Read
.acumen.md— strategy, positioning, stage, constraints. - Personas. Read
.acumen/personas.md— who we serve, their behaviors, workarounds, pain points. - Features. Read
.acumen/features.md— what exists today, gaps, decay.
More from vgrss/acumen
features
Build and maintain a lightweight feature inventory. Use after shipping, when planning, or to understand the current product surface.
9measure
Check KPI health — what's working, what's not, where to dig deeper. Suggests /workshop for opportunities. Use for metric reviews, health checks, or when something feels off in the numbers.
9diagnose
Find current problems in the product based on data, value delivery for main personas, and current features. Suggests /workshop for ideation on solutions.
9scout
Build and maintain a living competitor map. Supports both quick scans and deep competitive analysis. Use when entering a new market, a competitor launches something, before scoping a feature, or for strategic positioning decisions.
9persona
Build and maintain behavioral personas grounded in real user patterns. Use when launching, after user research, or when user understanding feels stale.
9narrate
Write product communication for a specific audience, including when stakes are high and stakeholders disagree. Use for exec summaries, eng briefs, customer announcements, or tradeoff negotiations.
9