strategize

Frames product design problems through research synthesis, opportunity sizing, and hypothesis definition.

Updated May 5, 2026
One-click install
npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill strategize-thegeekosaurus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: strategize
Source: https://github.com/TheGeekosaurus/blogging-platform-2/tree/main/.agents/skills/strategize
Command: npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill strategize-thegeekosaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump to building solutions before validating that a real problem exists, who has it, or whether the proposed solution fits. This Skill turns ambiguous business asks and scattered research into structured strategic briefs that ground all downstream design and development work in evidence. ## Core Features & Use Cases - Five Foundational Questions: Pressure-tests any project against problem validation, audience definition, solution fit, feature validation, and competitive landscape, with decision gates and loop-backs between them. - Design Brief Synthesis: Converts vague requests into a consistent output template covering context, gap, opportunity, goals, constraints, guiding principles, assumptions, and phased scope. - Anti-Pattern Detection: Flags common strategic failures like building for the wrong audience, solving non-problems, feature bloat, competitive blindness, and premature commitment. - 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, evaluate whether mobile is the right form factor, and produce a scoped Phase 1 brief before any design work begins. ## Quick Start Ask the AI to help you frame a new product idea or ambiguous business request into a strategic brief using the five foundational questions.

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 requirements?▼

Structure the brief around context, gap, opportunity, goals, constraints, guiding principles, key assumptions, and proposed Phase 1 scope. Ask clarifying questions mapped to each section rather than guessing, and document what you explicitly chose not to explore.

What questions should I ask before starting a new product project?▼

Pressure-test the project against five foundational questions: is the problem real, who exactly has it, is this the right solution form factor, is the feature set validated, and what already exists competitively. Each question has a decision gate that feeds the next.

How do I validate a product idea before building it?▼

Establish problem frequency, severity, and trajectory through desk research, intercept interviews, and surveys. Then define the audience segments with evidence, evaluate solution form factors against user context, and map the competitive landscape including indirect workarounds.

Does this skill conduct user research or interviews?▼

No, it synthesizes existing research rather than conducting primary research. When the foundational questions reveal knowledge gaps, it hands off to a research skill for interview scripts, usability tests, and surveys, then synthesizes the findings back.

What are common product strategy mistakes to avoid?▼

The five major anti-patterns are building for the wrong audience, solving a non-problem, feature bloat from stakeholder wish lists, competitive blindness, and premature commitment to solutions before validation. Each maps to a skipped foundational question.

When should I not use strategic framing?▼

Strategic framing is not for designing UI flows, defining visual identity, or making final tactical feature decisions. It sets direction and problem context; interaction design, visual design, and implementation specs belong to downstream disciplines.