strategize

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill strategize-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategize
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/strategize
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill strategize-danieliudi

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 structures the earliest phase of product design—turning ambiguous business asks and scattered research into grounded strategic briefs with explicit assumptions, scope boundaries, and testable hypotheses. ## 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 structured briefs covering context, gap, opportunity, goals, constraints, guiding principles, assumptions, and phased scope. - Anti-Pattern Detection: Flags strategic failure modes 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, question the form factor, map the competitive landscape, and produce a scoped Phase 1 brief before any design work begins. ## Quick Start Ask the strategist to frame a new product idea or ambiguous business request into a structured 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 an ambiguous request?

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 answer before starting a product design project?

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

How do I validate a product idea before building it?

Check problem frequency, severity, and trajectory through desk research, interviews, and surveys. Then define measurable hypotheses in the form "if we do X, then Y happens because of assumption Z" so each bet is testable rather than speculative.

Does this skill conduct user research or interviews?

No. It synthesizes existing research into strategic insights and recommends what primary research to commission, but interview scripts, usability tests, and surveys are delegated to a dedicated research skill. It flags evidence gaps transparently.

What are common product strategy mistakes to avoid?

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

When should I not use strategic framing?

Skip it when the problem is already validated and you need execution work like UI flow design, visual identity, or implementation specs. Those belong to downstream skills; strategic framing only sets direction and scope.