nw-discovery-workflow

Automate product-discovery planning with a 4-phase workflow and decision gates.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-discovery-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nw-discovery-workflow
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-discovery-workflow
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-discovery-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This 4-phase discovery workflow provides a repeatable method for teams to validate problems, map opportunities, test solutions, and assess market viability with clear gates and metrics.

Core Features & Use Cases

  • Four-phase workflow with built-in decision gates (G1–G4) and explicit phase transitions
  • Phase-specific success metrics and state-tracking templates to cap progress
  • Reusable structure for guiding cross-functional teams from problem to viability with documented outputs

Quick Start

Initiate nw-discovery-workflow to guide a team from problem validation through market viability and record outcomes.

Frequently Asked Questions about nw-discovery-workflow

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

FAQPage Schema
What is a phase-based product discovery workflow with decision gates?▼

A phase-based product discovery workflow with decision gates is a structured method to validate problems, map opportunities, test solutions, and assess market viability using four distinct phases with explicit transition criteria.

How do I structure product discovery validation from problem to market viability?▼

Structure product discovery validation by applying a deterministic 4-phase workflow with built-in decision gates (G1–G4), phase-specific success metrics, and state tracking to guide teams from initial problem validation to market viability.

Can I track progress across product discovery iterations using a lightweight schema?▼

Yes, you can track progress across discovery iterations using a lightweight YAML-based state-tracking schema that provides visibility into milestone-based metrics and phase transitions throughout the validation process.

Does this 4-phase discovery workflow work for cross-functional teams assessing market viability?▼

Yes, the 4-phase discovery workflow is designed for cross-functional teams assessing market viability, providing a reusable structure with documented outputs, milestone-based metrics, and defined gates to cap progress across iterations.

What's the best way to enforce phase transitions during product management discovery?▼

The best way to enforce phase transitions during product management discovery is to use built-in decision-gate logic (G1–G4) with explicit phase definitions, ensuring teams meet specific validation criteria before advancing to the next stage.

When should I not use a deterministic phase-based workflow for product discovery?▼

You should not use a deterministic phase-based workflow if your team lacks defined success metrics or needs highly flexible, non-linear exploration, as this approach enforces strict state tracking and explicit gate transitions to cap progress.