What happens if the ARGUMENTS are vague or missing?

The process prompts for clarifying questions and does not generate a full brief until inputs are specific.

Who conducts the research?

Research is delegated in parallel to @researcher for competitive analysis and @bizops for market viability and pricing, with confidence levels included for key claims.

What is the final deliverable?

A structured discovery brief with sections (Problem Statement, Target Audience, Competitive Landscape, Market Size Estimate, Unique Angle, Risk Factors, Go/No-Go) and a go/no-go recommendation, saved to .solopreneur/discoveries/{date}-{slug}.md, followed by the next-step prompt.

discover

npx machina-cli add skill pcatattacks/solopreneur-plugin/discover --openclaw

Files (1)

SKILL.md

2.0 KB

Discovery: $ARGUMENTS

You are running a discovery sprint for the CEO. Your goal is to determine whether this idea is worth pursuing.

Process

If $ARGUMENTS is vague or missing, ask clarifying questions before proceeding. Do not generate a full brief from vague input like "something with AI."
Delegate research in parallel:
- Delegate to @researcher with the idea description and target audience. Task: competitive landscape analysis of top 3-5 existing solutions — their positioning, pricing, strengths, weaknesses, and user sentiment. Include confidence levels for key claims.
- Delegate to @bizops with the idea description and target audience. Task: business viability assessment — market size (TAM/SAM/SOM with stated assumptions), revenue model options, pricing analysis, and a go/no-go recommendation with rationale.
Synthesize findings into a discovery brief with these sections:
- Problem Statement: What pain point does this solve?
- Target Audience: Who has this pain? How badly?
- Competitive Landscape: Top 3 competitors with comparison table
- Market Size Estimate: TAM/SAM/SOM with assumptions stated
- Unique Angle: What would make our approach different?
- Risk Factors: What could go wrong?
- Go/No-Go Recommendation: Clear recommendation with rationale
Save the brief to .solopreneur/discoveries/{date}-{slug}.md (create the directory if needed).

End with the next step prompt:

-> Next: Turn this into a product spec with:
   /solopreneur:spec .solopreneur/discoveries/{filename}

Or want the team to debate these findings first?
   /solopreneur:kickoff discovery sprint
   (assembles your full team for collaborative discussion — takes longer, deeper analysis)

Source

git clone https://github.com/pcatattacks/solopreneur-plugin/blob/main/skills/discover/SKILL.mdView on GitHub

Overview

This skill runs a discovery sprint to decide if an idea is worth pursuing. It coordinates parallel competitive analysis and business viability research, then compiles a structured discovery brief that guides go/no-go decisions.

How This Skill Works

If the inputs are vague, you first ask clarifying questions. Then you delegate research in parallel to @researcher (competitive landscape of top 3-5 solutions) and @bizops (TAM/SAM/SOM, pricing options, revenue models, and a go/no-go rationale). Finally, you synthesize findings into a discovery brief with defined sections and save it to the .solopreneur/discoveries folder, ending with the next-step prompt.

When to Use It

When you want to decide whether an idea is worth pursuing and need structured justification.
When you require competitive landscape analysis to understand positioning, pricing, and sentiment.
When you need a market size estimate (TAM/SAM/SOM) with explicit assumptions before committing resources.
When validating a product feature or concept against real-world market needs.
When preparing a go/no-go decision and recommended next steps for leadership.

Quick Start

Step 1: Provide a specific ARGUMENTS input; if vague, respond with clarifying questions.
Step 2: Instruct @researcher and @bizops to begin parallel assessments with clear deliverables.
Step 3: Review the discovery brief (Problem Statement, Target Audience, Competitive Landscape, Market Size, Unique Angle, Risks, Go/No-Go) and decide on next steps. -> Next: Turn this into a product spec with: /solopreneur:spec .solopreneur/discoveries/{filename} Or invite the team to debate findings with /solopreneur:kickoff discovery sprint.

Best Practices

Start with a precise Problem Statement and clearly defined Target Audience.
If inputs are vague, ask clarifying questions before proceeding.
Always benchmark against 3-5 competitors with data on positioning, pricing, strengths, and weaknesses.
State explicit TAM/SAM/SOM assumptions and explore multiple revenue models.
Document risk factors and deliver a clear Go/No-Go recommendation with rationale.

Example Use Cases

Idea: AI-assisted meeting note tool — assess competitive landscape, pricing, and market demand for SMBs.
Idea: Niche freelance marketplace — evaluate viability against established platforms and identify unique angles.
Idea: Vertical SaaS analytics for ecommerce stores — quantify market size and preferred pricing models.
Feature concept: Real-time collaboration in a project planner — compare with incumbents and user sentiment.
Opportunity: Local services marketplace — analyze demand, competition, and potential revenue streams.

Frequently Asked Questions

Add this skill to your agents