skills.rest
kryptonum-dev
kryptonum-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

10x-frame

Separate observed problems from stated causes and proposed directions before planning.

1|Updated Feb 26, 2025
Search Tags:#planning#root cause#hypothesis testing#decision support#scope#problem framing#brief generation
One-click install
npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-frame
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 10x-frame
Source: https://github.com/kryptonum-dev/fabryka-atrakcji/tree/main/.agents/skills/10x-frame
Command: npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-frame

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents wasted planning by separating the reported observation from the user’s stated cause and proposed direction, so you build solutions for the correct problem.

Core Features & Use Cases

  • Observation vs. Stated Cause Separation: Extracts the literal effect or scope question independently from hypotheses about why it’s happening and what to do.
  • Pre-Dispatch Clarifying Questions: Asks a short narrowing round (2–3 questions) to disambiguate the observation/scope without drifting into solutioning.
  • Evidence-Driven Dimension Mapping: Builds a tailored hypothesis space and tests plausible origins for where the framing could break.
  • Frame Brief Artifact for Handoff: Produces a single structured “Frame Brief” that preserves assumptions and the reframed problem statement for downstream planning.

Quick Start

Invoke 10x-frame with a short description of the observation, your initial framing (cause/approach), and your proposed direction, and it will produce a reframed problem statement ready for /10x-plan.

Frequently Asked Questions about 10x-frame

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why should I separate problem framing from proposed solutions before planning?▼

Separating problem framing from proposed solutions prevents wasted planning by isolating the reported observation from assumed causes, ensuring you build solutions for the correct problem rather than a biased direction.

How do I reframe a bug report into an evidence-backed problem statement?▼

To reframe a bug report, extract the literal observation independently from stated causes, ask clarifying questions to disambiguate scope, map hypotheses against evidence, and produce a structured problem statement.

What is a Frame Brief and how does it support project handoff?▼

A Frame Brief is a structured artifact that preserves extracted assumptions and the reframed problem statement, supporting safe handoff to downstream planning without proposing premature solutions.

Can I use root cause hypothesis testing for assumption challenges in product management?▼

Yes, root cause hypothesis testing applies to assumption challenges by building a tailored hypothesis space and testing plausible origins to validate where the initial problem framing could break.

What are the limitations of using problem framing for scope decisions?▼

Problem framing for scope decisions is limited to separating observations from proposed directions and does not propose solutions, requiring a downstream planning step to execute the validated Frame Brief.

Related Skills

Explore More Product & Management Skills→
pfrackpfrack

10x-frame

Separate observation from stated cause and proposed solutions in problem framing.

Community
Advanced
NickCrewNickCrew
29

assumption-buster

Transform assumptions with opposite, zero, or 10x operators to generate reframed ideas.

Community
Basic
yknothingyknothing
1

user-research

Generate a research plan, user personas, and journey map from user evidence.

Community
Advanced
EchoNoReturnEchoNoReturn

discovery-process

Coordinates a six-phase product discovery workflow from hypothesis framing to validated Go/No-Go decisions.

Community
Advanced