strategize

Frames product design problems through research synthesis, opportunity sizing, and structured strategic briefs.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/ishfuseini/usecase-gen --skill strategize-ishfuseini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategize
Source: https://github.com/ishfuseini/usecase-gen/tree/main/agent/skills/strategize
Command: npx skills add https://github.com/ishfuseini/usecase-gen --skill strategize-ishfuseini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into building products before validating whether the problem is real, who has it, or what already exists. This Skill turns ambiguous business asks and scattered research into grounded strategic briefs, preventing wasted effort on non-problems, wrong audiences, and bloated feature sets. ## Core Features & Use Cases - Five Foundational Questions: Pressure-tests any project against problem validation, audience definition, solution fit, feature validation, and competitive landscape before resources are committed. - Design Brief Synthesis: Converts vague requests and research findings into structured briefs covering context, gap, opportunity, goals, constraints, and scope. - Opportunity Sizing & Hypotheses: Quantifies problem scope and defines testable hypotheses with explicit assumptions. - Journey Mapping & Competitive Framing: Maps current user experience and plots direct and indirect competitors to find white space. - Use Case: A stakeholder says "we should build a mobile app for field technicians." Use this Skill to validate the problem severity, define the actual audience segments, question the form factor, and produce a phased strategic brief before any design work begins. ## Quick Start Ask the strategist to frame a new product idea into a structured brief using the five foundational questions and the output template.

Frequently Asked Questions about strategize

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

FAQPage Schema
How do I write a product design brief from vague stakeholder requirements?

Structure the brief around context, gap, opportunity, goals, constraints, guiding principles, assumptions, and proposed scope. Ask clarifying questions mapped to each section rather than guessing, and document what was explicitly left out of scope.

What questions should I answer before starting a new product project?

Validate five things: whether the problem is real and severe, exactly who has it, whether the chosen solution form factor fits user context, whether the feature set matches actual demand, and what direct and indirect competitors already exist.

How do I validate a product idea before building it?

Gather evidence on problem frequency, severity, and trajectory through desk research, interviews, and surveys. Define testable hypotheses in the form "if we do X, then Y happens because Z" and make every assumption explicit.

Does this skill conduct user research or interviews?

No. It synthesizes existing research into strategic insights but does not plan or run interviews, surveys, or usability tests. Primary research execution is handed off to a dedicated research skill, with findings fed back into the strategic frame.

What are common strategic framing mistakes in product design?

The main anti-patterns are building for an assumed audience, solving a non-problem, feature bloat from stakeholder wish lists, ignoring competitors, and committing to solutions before validating the problem. Each maps to a skipped foundational question.