Borrowing it
Nothing to install: this file belongs to hollandkevint/thinkhaven. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hollandkevint/thinkhaven/main/.claude/commands/bmadProduct/tasks/validate-product-concept.mdgit clone --depth 1 https://github.com/hollandkevint/thinkhavenWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/hollandkevint/thinkhaven/validate-product-concept)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/validate-product-concept"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/validate-product-concept.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.02029 |
| Opus 5 | $0.00000 | $0.01014 |
| Sonnet 5 | $0.00000 | $0.00406 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
validate-product-concept scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/validate-product-concept Task
When this command is used, execute the following task:
Validate Product Concept Task
Purpose
To systematically validate a product concept through customer discovery, market research, and prototype testing before significant development investment. This task follows lean startup principles to reduce risk and increase confidence in product-market fit potential.
Inputs
- Initial product concept or idea
- Target customer segment hypotheses
- Problem statement and value proposition
- Competitive landscape understanding
- Available resources and timeline
- Success criteria and validation thresholds
Key Activities & Instructions
1. Define Validation Framework
1.1 Core Hypotheses
<critical_rule>Make all assumptions explicit and testable</critical_rule>
Define key hypotheses to test:
- Problem Hypothesis: "We believe that [target customers] experience [problem] when [context]"
- Solution Hypothesis: "We believe that [solution approach] will help [target customers] achieve [outcome]"
- Value Hypothesis: "We believe that [target customers] will [use/pay for] our solution because [value proposition]"
- Growth Hypothesis: "We believe that [target customers] will [recommend/share] our solution via [channel/mechanism]"
1.2 Success Criteria
Define validation thresholds:
- Minimum percentage of customers confirming problem significance
- Required level of interest in proposed solution
- Willingness to pay indicators
- Time to value expectations
- Market size validation requirements
2. Customer Problem Validation
2.1 Problem Discovery Interviews
Conduct structured interviews to understand:
- Current customer workflows and processes
- Pain points and frustrations in existing approach
- Impact and consequences of current problems
- Attempted solutions and workarounds
- Priority level compared to other problems
Interview Framework:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 329 lines · 0 tokens per session scan A 04bd87a62a4c
validate-product-concept is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,029 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.