Product & Planning

drmoisan Skill

Capture unspecified or contradictory behavior and reconcile it into product decisions in the discovery workflow. Use when recording unspecified-behavior findings from the parity matrix and reconciling them into product-decision records via the reconciler role. Sixth stage, after parity and before the validation gate.

drmoisan Skill

Produce runtime characterization scenarios and evidence references in the discovery workflow. Use when characterizing observed runtime behavior of the legacy application into scenarios with supporting evidence and routing analysis to the runtime role. Fourth stage, after coverage and before parity.

markus41 Skill

Patterns from "Agentic Design Patterns" (Gulli & Sauco, 2025) applied to plugin marketplace architecture — federated registry, supply chain security, intent-based composition, and trust-scored plugin discovery.

gabeujin Skill

Prompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.

gabeujin Skill

Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.

the-utopia-studio Bundle

Use this skill when sales call quality is inconsistent, coaching feedback is vague, reps and managers disagree on what a good call is, or the user asks to \"build a call scorecard\", \"score this call\", \"review my rep's calls\", or \"make coaching more consistent\". It builds behavior-based scorecards for each key conversation type (prospecting, discovery, demo, pricing, close) and uses them to score real calls, localize where reps get stuck, and run chunked practice. Also fires when the user pastes a call transcript and wants it graded.

the-utopia-studio Bundle

Stands up the post-launch loop for a shipped AI product — ship behind sign-off → observe tweak-time (how much the customer edits before accepting) → learn by re-running the WHOLE eval set on every model release → refine by promoting autonomy only as a scored eval result, never by feel. Fires on "what happens after launch", "improve the product", "set up the loop", "a new model dropped, should we upgrade", "can we raise the autonomy / drop the sign-off yet". Returns a filled flywheel cadence doc. NOT for which metrics/North Star/retention to track (use metrics-that-matter), NOT for turning one trace into a discovery interview (use trace-to-interview), NOT for writing the eval set or autonomy ladder in the first place (use eval-first-spec — this re-runs what that created).

the-utopia-studio Bundle

Use this skill when you want a production-grade account scoring system instead of a vibes-based one: it tiers every account onto a Bronze/Silver/Gold/Diamond ladder, scoring pre-conversion accounts on intent signals + ACV potential and trials/customers on activation depth + expansion headroom. It encodes the judgment that makes scoring trustworthy — a hard self-serve gate with LinkedIn headcount verification, an enterprise persona gate, anonymous-signal and social-engagement caps, prior-relationship floors, and never-demote rules — with every threshold exposed as a tunable default. Each run produces a verified tier tag and ACV tag, a prepended signal-stack snapshot in account memory, a CRM lead-score sync, and correctly routed Gold/Diamond alerts with per-stakeholder engagement recommendations.

the-utopia-studio Bundle

Scores a specific concept across the four build-risk lenses — Desirability, Usability, Feasibility, Viability — where each lens is graded ONLY by its named tool (onion+JTBD+Kano for Desirability, a watched usability observation for Usability, a dev spike for Feasibility, ICE anchored to measured value for Viability) and run by its dual-track owner (Product/Design discovery beside Engineering delivery). Fires on "is this desirable / usable / feasible / viable", "should we build it", "run the four lenses", "go or no-go on this concept", "is this worth building". Output is a filled Four-Lens Scorecard: per-lens tool, owner, evidence + ladder weight, score, and an AND gate that KILLS the go if any single lens fails, every claim tagged [Fact]/[Assumption]/[Hypothesis]. NOT for the full problem→vision→strategy→roadmap spine (use product-frame-stack), NOT for scoring the PROBLEM on 8 dimensions (use problem-quality-scorecard), NOT for the five-question so-what gut check on the whole idea (use so-what-stress-test).

the-utopia-studio Bundle

Coach Studio fellows through the Cobuild curriculum as Salim — Utopia's fellow coach. Use when a fellow says 'I'm stuck', 'what should I do next?', 'review my [discovery/PRD/pitch]', 'I'm in M[X] and...', 'help me think through [problem]', 'can you check my [JTBD/canvas]?', or any pedagogy-style question. Salim is Socratic — he asks before telling, never produces artifacts the fellow should produce themselves, and is disciplined about Discovery before Build. He's module-aware (M1-M9) and points fellows to the right skills and frameworks. Outputs persistent cobuild logs to Proof.

the-utopia-studio Bundle

Build a responsive, interactive pitch-deck website from a brand book + a PRD/example deck. Use when the user asks to "build a pitch deck", "make an investor deck", "create a sales deck", generate a deck site from a brand book, or scaffold a deck from a PRD or existing slides. Pulls brand tokens (colors, typography, voice) from a brandbook-builder-style repo, runs a guided brief (investor vs sales, copy approval, image/logo intake, reference mining), then scaffolds a Vite + React + TS + Tailwind + motion deck site mirroring the utopia-os-deck section-scroll pattern.

the-utopia-studio Bundle

Fires when a fellow asks which numbers matter for a launched product — "what metrics should we track", "what should our North Star be", "is our retention any good / does the curve flatten", "our MAU is up-and-to-the-right, is that real or vanity", "what's our cost per outcome". Returns a metric scorecard: one customer-centric North Star, an AARRR one-metric skeleton, the flattening-retention truth test that GATES the North Star, and cost-per-outcome priced to the cent. Do NOT fire to design the post-launch improvement loop or promote autonomy (use refine-flywheel), to turn production traces into discovery interviews (use trace-to-interview), or to build the actual cohort dashboard, SQL, or alert thresholds (use the M9 retention-dashboard / cohort-analysis skills).

the-utopia-studio Bundle

Walks one validated problem up a load-bearing stack — validated problem → vision → strategy → product vision → North Star → OKRs → dual-track roadmap — and BLOCKS any layer from resting on an unvalidated problem below it. Fires on "frame the business", "vision to roadmap", "what's the strategy", "turn this validated problem into a roadmap", "give me the vision, North Star and OKRs". Output is a filled frame stack where every layer inherits the problem's evidence rung and every roadmap item ladders to a North Star. NOT the go/no-go that validates the problem in the first place (use problem-quality-scorecard / so-what-stress-test — this consumes their verdict), NOT the desirable/feasible/viable score (four-lenses-test), NOT the post-launch metric-tree and retention check (metrics-that-matter).

the-utopia-studio Skill

Summarize a customer interview transcript into a structured template with JTBD, satisfaction signals, and action items. Use when processing interview recordings or transcripts, synthesizing discovery interviews, or creating interview summaries.

the-utopia-studio Skill

Interview the user and produce an Agent PRD — the planning document that must exist before any agent code is written. Use when the user wants to build, scope, spec, or plan a new agent, generator, critic, pipeline stage, harness, or autonomous system; when they say "new agent", "agent PRD", "spec this agent", "plan this agent", "I want to build an agent that...", or ask what questions they should answer before starting. Also use when an existing agent is being rebuilt or a stage is being added to a pipeline. Do not use for writing agent implementation code — this skill produces a document only.

markus41 Skill

Create a client proposal for a fixed-scope automation engagement with ROI projections, timeline, and investment summary. Use when converting a discovery call into a formal proposal document for an insurance, mortgage, or financial services prospect.

boshi-xixixi Bundle

Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula. Use when someone asks to prioritize, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritization, A3 / lean countermeasure ranking, ROI vs. effort scoring, or building a remediation / improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture review gaps, or any free-form `{impediment, countermeasure}` list.

boshi-xixixi Bundle

Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via `list_skills` / `tool_search`, and oversized-response handling. Load this skill first when connecting an agent to Power Automate. For specialized workflows, load `flowstudio-power-automate-build`, `flowstudio-power-automate-debug`, `flowstudio-power-automate-monitoring` (Pro+), or `flowstudio-power-automate-governance` (Pro+) — each contains the workflow narrative, this skill provides the plumbing they all rely on. Requires a FlowStudio MCP subscription or compatible server — see https://mcp.flowstudio.app

boshi-xixixi Skill

Import existing Azure resources into Terraform using Azure CLI discovery and Azure Verified Modules (AVM). Use when asked to reverse-engineer live Azure infrastructure, generate Infrastructure as Code from existing subscriptions/resource groups/resource IDs, map dependencies, derive exact import addresses from downloaded module source, prevent configuration drift, and produce AVM-based Terraform files ready for validation and planning across any Azure resource type.

boshi-xixixi Skill

Guides Qdrant search strategy selection. Use when someone asks 'should I use hybrid search?', 'BM25 or sparse vectors?', 'how to rerank?', 'results are not relevant', 'I don't get needed results from my dataset but they're there', 'retrieval quality is not good enough', 'results too similar', 'need diversity', 'MMR', 'relevance feedback', 'recommendation API', 'discovery API', 'ColBERT reranking', or 'missing keyword matches'

lvtd-llc Bundle

Prepare reproducible Go CLI artifacts across operating systems and architectures with toolchain-derived target matrices, capability profiles, portable config and cache discovery, CGO decisions, version metadata, artifact handoff, smoke tests, archives, checksums, containers, and versioned source installation. Use when cross-compiling, packaging binaries, defining the distribution contract, or reviewing portability before release automation.

lvtd-llc Bundle

Use when improving cold outreach, sales conversations, customer discovery, community moderation, referral asks, partnership messages, interviews, or relationship-based persuasion where similarity, compliments, familiarity, cooperation, association, or rapport may affect trust.

aaaaqwq Bundle

PRD Engine — Product Requirements That Ship

aaaaqwq Bundle

Universal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok, YouTube, LinkedIn, X/Twitter, Google Maps, Google Search, Google Trends, Reddit, Airbnb, Yelp, and 15+ more platforms. Use for lead generation, brand monitoring, competitor analysis, influencer discovery, trend research, content analytics, audience analysis, review analysis, SEO intelligence, recruitment, or any data extraction task.

carlvellotti Bundle

Module 2.1: Write a PRD. Guides the student through templates, Socratic questioning, multiple PRD drafts, and review.

gaelic-ghost Bundle

Install, launch, validate, and diagnose existing ACP agents across Zed, Xcode, and other clients. Use for registry discovery, custom launch commands, auth, capabilities, sessions, and logs.

abdullah4ai Skill

Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.

lvtd-llc Bundle

Prioritize an experimentation platform roadmap across rate, quality, cost, usability, process, infrastructure, and advanced methods. Use when deciding which experimentation capability to build next, whether to platformize interleaving or adaptive testing, how to align experimentation with company goals, or how to trade off speed versus rigor.

lvtd-llc Bundle

Verify and monitor running experiments for operational quality. Use when designing prelaunch QA, spot-check tooling, experiment canaries, A/A tests, leakage checks, interference monitoring, active experiment dashboards, alerts, or an experimentation quality roadmap.

lvtd-llc Bundle

Plan experiment throughput strategies for mature A/B testing programs. Use when testing capacity is constrained, teams are waiting for experiment slots, roadmap coordination is slowing learning, or a team must choose isolated, overlapping, parallel, or capacity-aware experiment scheduling without sacrificing result quality.

infrasity-labs Bundle

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

carlvellotti Bundle

2.1 Write a PRD. Use when the student types /start-2-1.

carlvellotti Bundle

Lesson 2.1: Write a PRD. Use when the student types /start-2-1.

carlvellotti Bundle

Module 2.1: Write a PRD - Partner with AI to write better PRDs using templates, context, and multi-perspective review. Use when the student types /start-2-1.

griddynamics Bundle

To validate story readiness for a sprint or to break work into a human WBS.

griddynamics Bundle

To establish what exists — affected areas, behavior, prior attempts, dependencies, data.