Skip to content

heyparsadev/claude-venture-plugin / venture/skills/customers

customers

Verified

This skill should be used when the user wants customer discovery work — interview guides, problem validation, personas, jobs-to-be-done, or synthesizing interview/survey feedback — e.g. "make a customer interview guide", "how do I validate this problem", "build personas", "analyze my interview notes", "synthesize user feedback", "گاید مصاحبه با مشتری", "اعتبارسنجی مشکل", "پرسونا بساز", "مصاحبه‌هام رو تحلیل کن", "با مشتری چی بپرسم". Produces interview guides, ICP hypotheses, and evidence-ranked synthesis in the venture workspace.

references/synthesis-template.md

View on GitHub
# Discovery Synthesis Template

```markdown
# Customer Discovery Synthesis — <Venture>
<date> · n = <N> interviews (+<surveys/logs>) · period: <range>
Sampling: <how participants were found — name the bias this creates>

## Executive summary
<3–5 bullets: top validated pain, who feels it worst, willingness-to-pay evidence,
biggest surprise, verdict on the core assumption.>

## Pains — ranked by frequency × severity
| # | Pain | Freq (n/N) | Severity evidence (behavior, not words) | Quote |
|---|---|---|---|---|
| 1 | | | <e.g. "pays assistant 10h/wk to chase no-shows"> | "<verbatim>" (P4) |

Severity = what they DO about it today: money spent, hours lost, hacks built, failed purchases.

## Current solutions & their real cost
| Solution in use | Users (n) | Cost (money/time) | Why it fails them |
|---|---|---|---|

→ Willingness-to-pay read: <what current spend implies about price tolerance — conservative>

## Segments that emerged
<who has it worst — compare against the ICP hypothesis; state divergence plainly.
"We assumed solo dentists; the pain concentrates in 2–5-chair clinics with reception staff churn.">

## Personas / Jobs-to-be-Done (only what data supports — usually 1–2)
### <Persona name — one line>
- When <situation>, I want <motivation>, so I can <outcome>.
- Hires a solution when: <criteria> · Fires it when: <criteria>
- Buying reality: <who decides, who pays, what blocks>

## Disconfirming evidence (mandatory — empty section = suspicious questions)
<who didn't care and why; assumptions that cracked; enthusiasm that died at the commitment ladder>

## Assumption verdicts
| Assumption (from VENTURE.md) | Verdict | Evidence |
|---|---|---|
| | validated / refuted / unknown | |

## Commitment scoreboard
<n who climbed: follow-ups booked, intros given, pilots/pre-orders agreed — the honest demand signal>

## Implications
<what to build/test/drop next; which venture module to run with what question>
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall