nw-discovery-workflow

Orchestrate a four-phase discovery workflow with decision gates and state tracking.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-discovery-workflow-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-discovery-workflow
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-discovery-workflow
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-discovery-workflow-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams struggle to align stakeholders and de-risk early ideas without a repeatable process. nw-discovery-workflow provides a structured, four-phase discovery framework that guides problem validation, opportunity mapping, solution testing, and market viability with clear gates and metrics.

Core Features & Use Cases

  • Phase-based workflow with four clearly defined stages and gate transitions.
  • Decision gates G1–G4 to enforce go/no-go criteria and risk assessment.
  • Built-in state-tracking schema and success metrics to document progress and enable accountability.
  • Use Case: for a new product idea, run interviews, map top opportunities, prototype tests, and validate market viability before committing resources.

Quick Start

Begin Phase 1 by validating the problem through at least five customer interviews and record the findings as Phase 1 artifacts.

Frequently Asked Questions about nw-discovery-workflow

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

FAQPage Schema
How do I structure a product discovery workflow to validate early-stage ideas?

A product discovery workflow validates early-stage ideas through a structured, four-phase process: validating problems, mapping opportunities, testing solutions, and assessing market viability using defined decision gates.

What are decision gates in product management and how do they reduce risk?

Decision gates in product management are phase-based milestones (G1–G4) that enforce go/no-go criteria, ensuring risk assessment and stakeholder alignment before committing resources to the next stage of discovery.

How do I start the problem validation phase for a new product idea?

To start problem validation, conduct at least five customer interviews to validate the problem space, then record the findings as Phase 1 artifacts to establish foundational discovery evidence.

Can this discovery workflow be used for internal innovation experiments?

Yes, this discovery workflow applies to internal innovation experiments and startup environments, providing a repeatable process to map opportunities and assess market viability where stakeholder alignment is essential.

What is the best way to track progress across a four-phase discovery cycle?

The best way to track discovery progress is using a built-in state-tracking schema that documents success metrics across all four phases, enabling accountability and clear gate transitions.

Why do product teams struggle with early idea validation without a structured process?

Product teams struggle with early idea validation because without a repeatable process, they lack clear milestones and success metrics to align stakeholders and systematically de-risk opportunities before resource allocation.