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/bmadPMF/tasks/draft-case-study.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/draft-case-study)<a href="https://agentmods.dev/commands/hollandkevint/thinkhaven/draft-case-study"><img src="https://agentmods.dev/badge/commands/hollandkevint/thinkhaven/draft-case-study.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.01229 |
| Opus 5 | $0.00000 | $0.00615 |
| Sonnet 5 | $0.00000 | $0.00246 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
draft-case-study 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 3d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/draft-case-study Task
When this command is used, execute the following task:
Draft Case Study Task
Purpose
To create an initial theoretical case study that serves as the foundation for your sales-based learning approach. This case study will evolve based on real customer feedback but provides a starting point for conversations.
Inputs
- Initial product idea or concept
- Target customer hypothesis
- Understanding of the problem space
- Any existing customer insights or conversations
- Competitive landscape awareness
Key Activities & Instructions
1. Choose Your Target Person
- <critical_rule>Pick ONE REAL PERSON as your target, not a composite or persona</critical_rule>
- Identify Specifically: Choose someone you know or can clearly visualize
- Decision Maker Focus: Ensure they have budget authority
- Reachable: You should be able to contact similar people
Questions to answer:
- Who is this specific person? (Name, role, company type)
- Why did you choose them as your ideal customer?
- What makes them reachable for you?
2. Define the Project (What They're Trying to Accomplish)
Map out the specific project your target customer needs to complete:
- Project Name: How would they describe it internally?
- Project Scope: What does "done" look like?
- Success Criteria: How do they measure completion?
- **<important_note>Focus on their language, not your product features</important_note>
Example format: "[Role] wants to [accomplish specific outcome] so that [business impact]"
3. Establish Context (Why This Project, Why Now)
Identify what causes this project to become a priority:
3.1 Catalysts
- External pressure (regulation, competition, market change)
- Internal mandate (new leadership, strategy shift)
- Growth blocker (can't scale without solving this)
- Risk event (security breach, major failure)
3.2 Timing Factors
- Specific deadline or event
- Budget availability window
- Team bandwidth opening
- Strategic planning cycle
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.
- 3d ago First seen · 182 lines · 0 tokens per session scan A 696336fc89a4
draft-case-study is a command published in the GitHub repository hollandkevint/thinkhaven (5 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,229 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.