How the Product-Trio Approach Generates Solutions in the Brainstorm-Ideas-Existing Skill

The product-trio approach generates solutions by orchestrating parallel ideation across three disciplines—Product Manager, Product Designer, and Software Engineer—each contributing five distinct perspectives, then converging on the top five ideas through rigorous cross-functional prioritization.

The brainstorm-ideas-existing skill in the phuryn/pm-skills repository implements a structured ideation workflow that converts discovery context into validated solution concepts. Built on Teresa Torres’s Continuous Discovery philosophy, this skill leverages the product-trio model to surface innovative yet feasible directions that single-discipline brainstorming often misses.

The Six-Step Ideation Workflow

The skill executes a disciplined pipeline defined in pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md. Each step transforms raw inputs into structured outputs through collaborative validation and parallel generation.

Context Ingestion

The workflow begins by capturing the user’s objective, target segment, and desired outcomes. If supplemental files—such as research data, opportunity trees, or personas—are supplied, the skill reads them automatically. A product URL triggers a background web search to enrich the discovery context (see lines 12‑15 of the skill definition).

Opportunity Confirmation

Before ideation begins, the trio validates the problem statement. This checkpoint confirms the specific product, market segment, and success metrics to ensure all subsequent ideas align with validated opportunities rather than assumed problems.

Three-Perspective Ideation

The core of the product-trio approach unfolds through parallel generation:

• Product Manager: Generates five ideas emphasizing business value, strategic fit, and customer impact.
• Product Designer: Creates five ideas focused on user experience, usability, and delight.
• Software Engineer: Proposes five ideas leveraging technical possibilities, data availability, and scalability.

This parallel structure produces fifteen diverse concepts that reflect distinct constraints and opportunities across business, design, and engineering domains.

Cross-Perspective Prioritization

All fifteen ideas undergo evaluation against four standardized criteria:

1. Strategic alignment with the stated objective
2. Potential impact on desired outcomes
3. Feasibility and effort required for implementation
4. Differentiation from existing solutions

The system selects the top five ideas across all viewpoints based on these weighted factors.

Output Enrichment

For each of the five selected ideas, the skill generates a structured output containing:

• A concise name and one-sentence description
• The rationale for selection (why it outperformed other candidates)
• Key assumptions that require validation in downstream discovery work

Delivery

The final structured list is presented to the user. When the output exceeds display thresholds, the skill automatically saves the results as a markdown document in the user’s workspace for asynchronous reference.

CLI Usage Examples

The repository ships a CLI wrapper that loads skills as commands. Below are practical invocations of the brainstorm-ideas-existing skill:

# Basic invocation – the trio will ask clarification questions as needed

pm-toolkit brainstorm-ideas-existing \
  --objective "Increase user retention for our SaaS dashboard" \
  --segment "Mid-size B2B teams" \
  --outcomes "30% higher 30-day active users"

# Providing supplemental research files (e.g., persona PDFs, opportunity tree)

pm-toolkit brainstorm-ideas-existing \
  --objective "Improve onboarding flow" \
  --segment "New trial users" \
  --outcomes "Reduce time-to-first-value to <5 minutes" \
  --files ./research/opportunity_tree.md ./research/personas.pdf

# Directing the skill to store the result in a markdown file

pm-toolkit brainstorm-ideas-existing \
  --objective "Add collaboration features" \
  --segment "Product teams" \
  --outcomes "20% increase in daily active collaborations" \
  --output ideas.md

Key Implementation Files

The skill’s behavior is governed by the following source files in the phuryn/pm-skills repository:

• pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md – Contains the full specification including context handling logic, three-perspective ideation steps, and prioritization algorithms.
• pm-product-discovery/README.md – Provides domain overview explaining how the skill integrates into the broader product-discovery toolkit.
• pm-toolkit/commands/*.md – Documents CLI usage patterns and parameter definitions for skill invocation.

Summary

• The product-trio approach synthesizes ideas from Product Management, Design, and Engineering to eliminate blind spots in single-discipline brainstorming.
• Each discipline generates five parallel ideas (fifteen total), evaluated against strategic alignment, impact, feasibility, and differentiation.
• The workflow is implemented in pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md and accessible via the pm-toolkit CLI.
• Outputs include structured rationales and validation assumptions to support continuous discovery cycles.

Frequently Asked Questions

What is the product-trio approach in the brainstorm-ideas-existing skill?

The product-trio approach is a collaborative ideation model where a Product Manager, Product Designer, and Software Engineer each contribute distinct perspectives to solution generation. As implemented in the brainstorm-ideas-existing skill, this ensures ideas balance business viability, user desirability, and technical feasibility from inception.

How many ideas does each role generate?

Each of the three roles generates exactly five ideas, resulting in fifteen total concepts during the ideation phase. The skill then prioritizes and filters these down to the top five highest-scoring solutions based on the four evaluation criteria.

What criteria determine which ideas are selected?

The skill evaluates all fifteen ideas against four specific criteria: strategic alignment with the objective, potential impact on outcomes, feasibility and implementation effort, and differentiation from existing solutions. The top five performers across these dimensions advance to the final output.

Where is the skill configuration defined?

The complete workflow specification resides in pm-product-discovery/skills/brainstorm-ideas-existing/SKILL.md. This file defines the context ingestion logic (lines 12‑15), the three-perspective generation rules, and the cross-prioritization methodology used by the product-trio approach.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}