Results for “defi”

Clarifies ambiguous or conflicting requests by researching first, then asking only judgment calls. Use when prompts say "grill me", ask hard questions, request relentless interrogation, pressure-test assumptions, clarify scope/requirements, define success criteria, or request system-design/optimization decisions.

Defines when to create Epic, Feature, UserStory, or Task tickets and adds concise guidance to SKILL.md.

Define company values and culture for a minimalist business, drawing on principles from The Minimalist Entrepreneur.

Build sales playbooks, define pipeline stages, and optimize conversion rates with structured processes and lead scoring.

Creates structured specifications before writing code to clarify requirements, surface assumptions, and define success criteria, reducing rework and miscommunication.

Locates files by intent using semantic search, ideal for finding implementations, definitions, or documentation in medium to large repositories.

Designs an approval-gated feature specification from approved requirements, covering architecture decisions, component boundaries, quality constraints, and definition of done.

Manage Azure API Center resources including services, workspaces, APIs, versions, definitions, environments, and deployments using the .NET SDK.

Defines the product vision, architecture, pricing, and roadmap for Auri, an intelligent voice assistant built on Amazon Alexa and Claude.

Draft an Amazon-style press release to define customer value and align stakeholders before building a product or feature.

Define, track, and interpret product metrics across discovery, growth, and mature product stages using frameworks like AARRR, North Star, and HEART.

Defines end-to-end user experience behavior and interaction logic, covering flow design, state machines, error recovery, validation, accessibility, and testable acceptance criteria.

Improves user onboarding and activation by defining the aha moment, designing effective onboarding flows, and building engagement loops to boost retention.

Semantic file discovery via `vexor`. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.

Conducts structured requirements workshops to produce feature specifications, user stories, EARS-format functional requirements, acceptance criteria, and implementation checklists.

Define a lightweight, disposable Proof of Life probe to test a risky hypothesis cheaply and surface harsh truths before building real product.

Defines ideal customer profile filters, scores inbound and outbound leads, and builds a lightweight qualification rubric to sharpen pipeline focus for founder-led sales.

This skill should be used when implementing features from a PRD spec, tracking implementation progress, or resuming work across sessions. Covers Dex task management for PRD story execution, daily workflows, and skill auto-loading.

Guide product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document.

Define o produto Auri, um assistente de voz inteligente baseado em Alexa e Claude, incluindo arquitetura AWS, planos de preços, roadmap e estratégia de mercado.

Define o produto Auri, um assistente de voz inteligente baseado em Alexa e Claude, incluindo visão, persona, arquitetura AWS, planos de preços, roadmap e estratégia de mercado.

Guide cross-functional teams through creating Jeff Gothelf's Lean UX Canvas v2 to frame business problems, surface assumptions, and define experiments.

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

Scans top 24-hour token movers across major chains via GeckoTerminal, applies pump-risk filters, and outputs a chain leaderboard with per-chain top 5 runners.

Use when building, refactoring, or documenting Graft apps and proxies, including when asked to create a tool server, API server, dual-protocol server, or MCP-HTTP bridge. Graft's core thesis: define tools once and serve them as both HTTP REST endpoints and MCP tools from the same server, with discovery, docs, and OpenAPI generated automatically. Covers concrete actions such as defining tools and handlers, configuring authentication middleware, setting up HTTP and stdio transports, generating OpenAPI documentation, wrapping existing APIs via proxy mode, and wiring up the full CLI workflow.

Use when driving a feature prompt to a production-ready PR through discovery, definition, design, spec, issues, and dev phases, or when the user runs /feature or /feature resume — orchestrates the A-Team agentic pipeline over a target repo.

Manage Gate entities — validation checkpoints that WorkItems, scopes, or policy applications must pass (code review, security scan, tests). Use when defining or updating a checkpoint for v2 workflow surfaces — code review, tests green, security scan, stakeholder approval.

Synthesize customer research data to define the Ideal Customer Profile (ICP) including demographics, behaviors, Jobs to Be Done, and pain points.

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

Define product positioning by mapping competitive alternatives, unique attributes, and best-fit customers to the right market category using a structured canvas and 5-step process.