Results for “discovery-sprint”

Turns vague features, bug clusters, roadmap items, or launch work into an execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.

Guide product managers through a complete discovery cycle from problem hypothesis to validated solution using problem framing, customer interviews, synthesis, and experimentation.

Workflow 1: Full idea discovery pipeline. Orchestrates research-lit → idea-creator → novelty-check → research-review to go from a broad research direction to validated, pilot-tested ideas. Use when user says "找idea全流程", "idea discovery pipeline", "从零开始找方向", or wants the complete idea exploration workflow.

Creates concise early UX discovery artifacts for PRD development, customer development, new product ideas, feature bets, and redesigns. Use when the user asks to hypothesize an ideal customer profile, generate proto-personas, write customer problem or jobs-to-be-done hypotheses, create journey maps, shape value propositions, or turn product context into design-sprint-style customer insight artifacts for product and engineering teams.

Plan customer discovery interviews with the right goal, segment, constraints, and method for problem validation, churn research, or new product ideas.

Generates feature ideas from PM, Designer, and Engineer perspectives for initial product discovery of a new product.

discovery-plan

Routes product-discovery work into the right stage — opportunity brief, research, PRD, tickets, or outcome review — and hands off to the matching sub-skill.

Runs focused experiments to validate feasibility of an idea, saving artifacts to .planning/spikes/ and supporting both idea and frontier modes.

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots to keep product decisions grounded in evidence.

Guides a structured interview and repository research to clarify feature requirements, classify scope, and produce context artifacts for approval before design.

Research-obsessed strategist for webinar discovery. Use for webinar research, hook generation, topic validation, angle finding, audience analysis, content discovery, competitive landscape. Triggers: 'webinar research', 'find angle', 'webinar hook', 'topic research', 'discovery phase'.

Requires python3, and AISA_API_KEY. Uses the supplied AISA_API_KEY to send requests to https://api.aisa.one. Native-first ClawHub plugin for `search`. Ships the packaged AIsa skill with an `openclaw.plugin.json` manifest and a Claude-compatible bundle fallback. Search command center for web, academic, Tavily, and Perplexity-backed research through one AIsa API key. Use when: the user needs one flagship skill for live search, source discovery, or citation-ready research. Supports fast lookup, answer generation, and deep research reports.

Scans a project for stack signals and pain points, searches the skills-hub registry and local skills, scores candidates, and presents a ranked shortlist with install commands.

Plan customer discovery conversations with hypotheses, prompts, probes, and capture fields.

Creative discovery partner for ideation and concept shaping. Use when brainstorming, exploring product ideas, expanding vague concepts, comparing directions, finding opportunities, creative ideation. Triggers: 'brainstorm', 'product ideas', 'concept exploration', 'idea expansion', 'creative thinking', 'product discovery', 'what if', 'I have an idea'.

Auto-mirror top Discovery traders on Hyperliquid. Scans top 50 traders, scores on PnL rank (35%), win rate (25%), consistency (20%), hold time (10%), drawdown (10%). Creates 2-5 mirror strategies with overlap checks. Daily rebalance with 2-day watch period before swaps. Use when setting up trader mirroring, copy trading, or portfolio auto-rebalancing based on Discovery leaderboard performance.

ateam-discovery

Coaches sales teams on elite discovery methodology — question design, current-state mapping, gap quantification, and call structure that surfaces real buying motivation.

<!-- TODO: Progressive discovery of MCP servers and registries -->

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing product value propositions. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint.

Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", or "interview script". Also trigger when preparing user research questions, interpreting ambiguous customer feedback, or designing customer discovery processes that avoid false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.