AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Problem Statement Builder

skill-patonkikh-apes-problem-statement-builder · by patonkikh

>

No reviews yet
0 installs
8 views
0.0% view→install

Install

$ agentstack add skill-patonkikh-apes-problem-statement-builder

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-patonkikh-apes-problem-statement-builder)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Problem Statement Builder? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Problem Statement Builder

Purpose

Transform a raw problem hypothesis into a structured, testable Problem Statement using Jobs-to-be-Done (JTBD) framing.

Input: Problem hypothesis, target user context, evidence (optional) Output: Problem Statement document with JTBD frame, success criteria, and scope boundaries Examples: See [examples.md](examples.md) for worked input/output.


Workflow

Step 1: Extract problem signals

Gather:

  • Who experiences the problem (user segment)
  • When/where the problem occurs (context)
  • Current workaround (how they cope today)
  • Cost of the problem (time, money, risk, emotion)
  • Evidence source (interviews, data, observation)

Step 2: Apply JTBD framing

Structure the problem as:

When [situation] I want to [motivation] so I can [expected outcome]

Identify:

  • Functional job (task to complete)
  • Emotional job (how they want to feel)
  • Social job (how they want to be perceived)

Step 3: Define problem boundaries

Specify:

  • In scope: what this problem statement covers
  • Out of scope: adjacent problems explicitly excluded
  • Root cause vs symptom: flag if current framing may be a symptom

Step 4: Write success criteria

Define measurable indicators that the problem is solved:

  • Leading indicators (behavior change)
  • Lagging indicators (outcome metrics)
  • Minimum viable improvement (what "good enough" looks like)

Step 5: Validate

Run Validation checklist.


Decision Rules

| Condition | Action | |-----------|--------| | Problem describes a solution, not a need | Reframe from solution to underlying job | | Multiple unrelated problems in input | Split into separate problem statements; complete one | | No target user specified | Stop; request user segment | | Problem is a symptom | Add "Root Cause Hypothesis" section; flag for discovery | | Success criteria are not measurable | Rewrite with specific metrics or observable behaviors |


Validation

  • [ ] JTBD sentence follows When/Want/So format
  • [ ] Functional, emotional, and social jobs identified
  • [ ] In-scope and out-of-scope boundaries defined
  • [ ] At least 2 measurable success criteria
  • [ ] Current workaround documented
  • [ ] Cost of problem articulated
  • [ ] No solution embedded in problem statement

Anti-patterns

  • Solution disguised as problem — "Users need an AI dashboard" instead of the underlying job.
  • Vague pain — "Users are frustrated" without specific context or cost.
  • Everyone's problem — no specific segment or situation.
  • Unmeasurable success — "better experience" without criteria.
  • Ignoring workarounds — not documenting how users cope today.

Best Practices

  • Quote user language when evidence is available.
  • Quantify cost of problem where possible (hours/week, error rate, churn).
  • Separate problem statement from proposed solution entirely.
  • Link to Idea Validation Report if available from prior Skill.
  • Flag assumptions that need user research validation.

Output Structure

# Problem Statement: [Short Title]

## JTBD Frame
**When** ... **I want to** ... **so I can** ...

## Job Types
| Type | Job |
|------|-----|
| Functional | |
| Emotional | |
| Social | |

## Problem Details
- **Who:** [segment]
- **Context:** [when/where]
- **Current workaround:** [how they cope]
- **Cost of problem:** [quantified if possible]

## Scope
- **In scope:**
- **Out of scope:**

## Success Criteria
| Criterion | Type | Target |
|-----------|------|--------|

## Root Cause Hypothesis
[If symptom detected]

## Assumptions
- [ ] [Assumption needing validation]

## Evidence
| Source | Finding |
|--------|---------|

Next Skills

| Outcome | Recommended Skill | |---------|-------------------| | Need user segment detail | product/persona-generator | | Problem validated, ready for vision | product/product-vision-builder | | Multiple solutions to compare | product/feature-prioritization | | Ready for requirements | product/prd-generator |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.