Acumen

Scope a single product increment end-to-end — context, spec, implementation, wireframes, and engineering considerations. Use when a feature or bet needs a shippable document before building — typically the option chosen out of /workshop's divergence. Leads to /critique-product.

Print a quick-reference cheatsheet of all Acumen skills, organized by layer.

Pull latest code from main, summarize recent changes in product-friendly terms, and report .acumen/ context health (what exists, what's fresh, what's stale, what's missing). Preserves all .acumen/ context files.

Evaluate and validate a PM artifact — score for rigor, test riskiest assumptions, and decide if it's ready to ship. Use when reviewing a PRD, spec, increment, strategy, or roadmap.

Find what's broken and what's underexploited — problems AND opportunities — grounded in data, value delivery per persona, and current features. The entry point to ideation; hands sharp problems and opportunities to /workshop.

One-time setup that gathers product context for your project and saves it to .acumen.md. Run once to establish persistent product guidelines.

Map per-persona value delivery to the usage and north star metrics that prove it. Use when you need to articulate what value each persona gets and how you know it's being delivered.

Diverge on a problem or opportunity — generate many genuinely different solution shapes before committing to one. Use after /diagnose surfaces a problem or opportunity, or when you have a problem and want to see the full range of ways to solve it before scoping.

Audit product identity — what we do, for whom, whether the feature surface is coherent with the thesis, and whether context files agree with each other. Use when the product feels unfocused, after a pivot, before strategic planning, or when something in the product story feels off.

Build and maintain DESIGN.md — a structured visual identity contract for coding agents. Use when codifying a design system, after a visual refresh, or before AI-assisted UI work.

PostHog integration for Next.js Pages Router applications

Walk through structured feedback and submit it as a GitHub Issue on the Acumen repo.

Ground all product work in rigorous thinking about users, problems, and outcomes. Generates specific, opinionated product artifacts that avoid generic AI template thinking. Use when any product skill requires project context.

Write a changelog from recent PRs and commits, grounded in feature context. Use after shipping, at the end of a sprint, or for release notes.

Audit what's hard to copy — moats, switching costs, data advantages, network effects, and AI-era resilience. Use when deciding where to invest, after a competitor move, or before fundraising.

Build and maintain behavioral personas grounded in real user patterns. Use when launching, after user research, or when user understanding feels stale.

Plan a sequence of bets, break into shippable increments, prioritize. Use when building a roadmap, sequencing work, triaging a backlog, or breaking an epic into increments.

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.

Fetch the latest Acumen skills from GitHub and update local copies (source, .agents, .claude symlinks).

Build and maintain a lightweight feature inventory. Use after shipping, when planning, or to understand the current product surface.

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.