product-proposal

Transforms product requests into decision-ready proposals with interactive mock-ups.

16|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/sbluemin/fleet-harness --skill product-proposal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-proposal
Source: https://github.com/sbluemin/fleet-harness/tree/main/.agents/skills/product-proposal
Command: npx skills add https://github.com/sbluemin/fleet-harness --skill product-proposal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires console-e2e, frontend-design, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill bridges the gap between a vague product request and a well-informed, decision-ready proposal. It uses measured data and interactive mock-ups to ensure that the final decision is grounded in reality and informed by user needs.

Core Features & Use Cases

  • Measure Present State: Uses the console-e2e skill to measure and document the current state of the product.
  • Essence vs. Surface: Differentiates between user-proposed solutions and underlying problems.
  • Interactive Mock-up: Creates an interactive mock-up of potential solutions using the frontend-design skill.
  • PO/PD Review: Provides a structured review process that includes scoring options on trade-off axes.
  • Decision-Ready Proposal: Outputs a detailed proposal that can guide the next steps in product development.

Quick Start

Use the product-proposal skill to analyze a product feature request, 'Asking for a "close confirmation checkbox" on the console'. Provide the request details and the skill will generate a decision-ready proposal.

Frequently Asked Questions about product-proposal

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

FAQPage Schema
How do I turn a vague product request into a decision-ready proposal?

To create a decision-ready product proposal, you need to measure the current state, analyze underlying user needs versus surface requests, and build an interactive mock-up. This grounds product decisions in measured data and validated solutions.

What is the best way to analyze user needs from a feature request?

Analyzing user needs requires differentiating between user-proposed solutions and the underlying problems. By measuring the present state and validating with an interactive mock-up, you ensure the analysis reflects actual user needs.

Do I need console-e2e and frontend-design to generate a product proposal?

Yes, executing this product proposal generation requires the console-e2e skill to measure the present state and the frontend-design skill to create interactive mock-ups for solution validation.

How do I validate a proposed solution before final product development?

You validate a proposed solution by creating an interactive mock-up using frontend-design, then structuring a PO/PD review that scores options on trade-off axes to ensure the final decision is well-informed.

Can I use this approach for issue reports and user complaints?

Yes, this approach applies to issue reports and user complaints requiring in-depth analysis. It transforms these inputs into decision-ready proposals by measuring the current state and validating solutions.

What limitations exist when creating interactive mock-ups for product decisions?

Creating interactive mock-ups for decision-ready proposals is limited by the dependencies on console-e2e for measuring current state and frontend-design for visualization. It is not suitable for requests lacking sufficient detail for in-depth analysis.