Skip to content
cccskills
FreePublished on GitHub

hypothesis-design

Formulate clear, testable hypotheses for product experiments. Use when designing experiments to validate solutions.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.5 KB
  • agents/openai.yaml196 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Product Hypothesis Design

Formulate clear, testable hypotheses for product experiments.

When to Use

When you have a product problem and need to design an experiment to validate a solution.

The Process

1. Identify the Experiment Goal

  • What user problem are you addressing?
  • What change do you think will help?

2. Draft Hypothesis Statement

Use this structure:

[Action] will cause [Outcome] to [Direction] for [Users] under [Conditions]

All 5 components required:

  • Action: What you're doing
  • Outcome: What metric changes
  • Direction: Increase/decrease/improve
  • Users: Who's affected
  • Conditions: When/where this applies

3. Check for Specificity

  • Is the action clearly defined?
  • Is the outcome measurable?
  • Are users and conditions specific?

4. Develop Measurement Plan

  • What metrics prove success?
  • How will you collect data?
  • What's the sample size?

5. Narrative Check

Convert to story format:

Currently, [user] is experiencing [problem].
We believe that by [change], we'll see [outcome].
We'll know we're right when [metric] changes by [amount].

Quality Check

  • Is the hypothesis falsifiable?
  • Can you measure the outcome?
  • Is the timeframe realistic?
  • Are success criteria clear?

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.

The English summary is being prepared. Showing the original description.

itseffi/agentic-os117Updated Oct 7, 2026

See all skills by itseffi

Report a problem with this skill