product-shape

Shape product ideas into viable MVPs with pricing, positioning, and stack architecture guidance.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/linardsb/fredis --skill product-shape
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-shape
Source: https://github.com/linardsb/fredis/tree/main/.claude/skills/product-shape
Command: npx skills add https://github.com/linardsb/fredis --skill product-shape

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms a validated product idea into a Minimum Viable Product (MVP) by providing structured guidance on pricing, positioning, and stack architecture, catering specifically to two-sided/marketplace products.

Core Features & Use Cases

  • Pricing: Utilizes Van Westendorp, Gabor-Granger, and Ramanujam pricing methods to determine the optimal price points.
  • Positioning: Implements April Dunford and Geoffrey Moore positioning strategies with a one-tweet test.
  • Stack Architecture: Offers Ries, Kniberg, and Wardley build-vs-buy stack architecture guidance.
  • Two-Sided Products: Applies the 8-canvas Platform Design Toolkit for ecosystem, liquidity, transaction-cost, and network-effect analysis.
  • Use Case: After validating an idea, use this Skill to develop a structured approach for pricing, positioning, and architecture of the product.

Quick Start

Use the product-shape skill to shape the product idea for the "Email Hub" service.

Frequently Asked Questions about product-shape

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

FAQPage Schema
How do I shape a validated product idea into a viable MVP?

To shape a validated product idea into a viable MVP, you need structured guidance on pricing, positioning, and stack architecture, tailored specifically to your product type and feature requirements.

What is the best way to determine pricing strategy for a two-sided marketplace MVP?

Determining pricing strategy for a two-sided marketplace MVP involves using frameworks like Van Westendorp, Gabor-Granger, and Ramanujam pricing methods to find optimal price points for your platform.

How do I position a new software product before building the MVP?

Positioning a new software product before building the MVP involves applying April Dunford and Geoffrey Moore positioning strategies, validated through a one-tweet test to ensure market clarity.

Can I use build vs buy analysis for my marketplace stack architecture?

Yes, you can guide your marketplace stack architecture decisions using build vs buy analysis frameworks developed by Ries, Kniberg, and Wardley to map out your technical requirements.

When do I need to use the Platform Design Toolkit for product development?

You need the Platform Design Toolkit for product development when building two-sided products that require ecosystem, liquidity, transaction-cost, and network-effect analysis across 8 canvases.

Does this MVP development approach support two-sided marketplace products?

Yes, this MVP development approach explicitly supports two-sided marketplace products by applying the 8-canvas Platform Design Toolkit for ecosystem and network-effect analysis.