bk-explore

Guide conversational exploration of feature ideas through targeted questions.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/dikini/knot --skill bk-explore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bk-explore
Source: https://github.com/dikini/knot/tree/main/.agents/skills/bk-explore
Command: npx skills add https://github.com/dikini/knot --skill bk-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users clarify vague ideas and requirements through guided conversation before committing to formal design or research.

Core Features & Use Cases

  • Idea Refinement: Flesh out nascent concepts and understand underlying problems.
  • Requirement Clarification: Define user needs, success metrics, and constraints.
  • Use Case: When you have a rough idea for a new feature, use this Skill to discuss its purpose, target users, and potential approaches with the AI, leading to a clearer understanding before proceeding.

Quick Start

Use bk-explore to discuss a new feature idea for the note-taking app.

Frequently Asked Questions about bk-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clarify vague product requirements before starting formal design?

Conversational exploration helps refine ideas by asking targeted questions about user needs, success metrics, and constraints. This structured dialogue bridges vague concepts to actionable next steps before committing to formal research or design.

What is the best way to flesh out a rough feature idea for a new product?

The best way to flesh out a rough feature idea is through guided conversational ideation. By discussing the feature's purpose, target users, and potential approaches, you synthesize emerging understanding into a clearer concept for product development.

How do I structure a brainstorming session to refine feature ideation?

To structure brainstorming for feature ideation, engage in a guided dialogue that explores the underlying problem and target users. This methodical questioning refines nascent concepts into defined requirements and actionable steps.

Can I use conversational exploration to define success metrics for a new feature?

Yes, you can use conversational exploration to define success metrics for a new feature. The process involves targeted questions that clarify user needs and constraints, helping you synthesize emerging understanding into measurable requirements.

When do I need guided dialogue for product development exploration?

You need guided dialogue for product development exploration when you have a vague concept and want to understand underlying problems before committing to formal design. It applies to the initial stages of feature ideation and requirement clarification.

Are there limitations to using conversational ideation for requirement clarification?

A limitation of conversational ideation is that it requires a structured dialogue to be effective, serving only the initial stages of product development. It bridges vague concepts to actionable next steps but does not replace formal design or research.