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/design-discovery-plan.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/design-discovery-plan)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/design-discovery-plan"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/design-discovery-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/design-discovery-plan"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/design-discovery-plan.svg" alt="Reviewed on agentmods" width="80" 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.01783 |
| Opus 5 | $0.00000 | $0.00892 |
| Sonnet 5 | $0.00000 | $0.00357 |
| Haiku 4.5 | $0.00000 | $0.00178 |
Grade A, and why
design-discovery-plan 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 6d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-discovery-plan Task
When this command is used, execute the following task:
Design Discovery Plan Task
Purpose
To create a systematic customer discovery plan using SVPG continuous discovery methodologies. This plan establishes regular customer interaction patterns, research methods, and learning objectives to drive evidence-based product decisions.
Inputs
- Product opportunity or problem space to explore
- Target customer segments and personas
- Key assumptions and hypotheses to test
- Business objectives and success criteria
- Available resources and timeline constraints
- Existing customer research and insights
Key Activities & Instructions
1. Define Discovery Objectives
1.1 Primary Learning Goals
<critical_rule>Focus on outcomes and customer value, not solution validation</critical_rule>
Answer these questions:
- What customer problems are we trying to understand?
- What decisions will this discovery inform?
- How will insights change our product strategy?
- What assumptions are we testing?
Example format: "We want to understand [customer behavior/need] so we can [make informed decision] to achieve [business outcome]"
1.2 Success Criteria
Define what good discovery looks like:
- Specific insights we need to uncover
- Quality of evidence required for decisions
- Timeline for gathering insights
- Coverage across customer segments
2. Map Research Questions
2.1 Customer Understanding Questions
- What jobs are customers trying to get done?
- What obstacles prevent them from success?
- How do they currently solve these problems?
- What triggers them to seek solutions?
- What would make them switch from current approach?
2.2 Solution Validation Questions
- How well does our proposed solution fit their workflow?
- What value would they expect from this solution?
- What concerns would they have about adoption?
- How would they measure success?
- What would make this a "must-have" vs. "nice-to-have"?
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.
- 6d ago First seen · 302 lines · 0 tokens per session scan A 1859067e81e8
design-discovery-plan is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,783 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.