Skip to content
cccskills
FreePublished on GitHub

nw-discovery-workflow

4-phase discovery workflow with decision gates, phase transitions, success metrics, and state tracking

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md4.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Discovery Workflow

4-Phase Overview

PHASE 1              PHASE 2              PHASE 3              PHASE 4
Problem Validation   Opportunity Mapping  Solution Testing     Market Viability
      |                    |                    |                    |
      v                    v                    v                    v
"Is this real?"      "Which matters?"     "Does it work?"      "Viable business?"

Phase Details

Phase 1: Problem Validation

Duration: 1-2 weeks | Min interviews: 5 | Techniques: Mom Test, Job Mapping Core question: Is this a real problem worth solving?

Phase 2: Opportunity Mapping

Duration: 1-2 weeks | Min interviews: 10 cumulative | Techniques: OST, Opportunity Algorithm Core question: Which problems matter most?

Phase 3: Solution Testing

Duration: 2-4 weeks | Min interviews: 5 per iteration | Techniques: hypothesis testing, prototypes Core question: Does our solution actually work?

Phase 4: Market Viability

Duration: 2-4 weeks | Min interviews: 5 + stakeholders | Techniques: Lean Canvas, 4 Big Risks Core question: Can we build a viable business?

Decision Gates

G1: Problem to Opportunity

Proceed: 5+ confirm pain + willingness to pay | Pivot: problem differs from expected | Kill: <20% confirm

G2: Opportunity to Solution

Proceed: top 2-3 score >8 (max 20) | Pivot: new opportunities discovered | Kill: all low-value Scoring: Score = Importance + Max(0, Importance - Satisfaction). Each 1-10. >8 = high importance with satisfaction gap.

G3: Solution to Viability

Proceed: >80% task completion, usability validated | Pivot: needs refinement | Kill: fundamental blocks

G4: Viability to Build

Proceed: all 4 risks addressed, model validated | Pivot: model needs adjustment | Kill: no viable model

Success Metrics

Phase 1: Problem Validation

MetricTarget
Problem confirmation>60% (3+ of 5)
FrequencyWeekly+
Current spending>$0 on workarounds
Emotional intensityFrustration evident

Done when: 5+ interviews, >60% confirmation, articulated in customer words, 3+ examples. Threshold: 60% aligns with Mom Test -- 3/5 consistent signals = proceed, <20% = kill. Combined with qualitative markers.

Phase 2: Opportunity Mapping

MetricTarget
Opportunities identified5+ distinct
Top scores>8 / max 20
Job step coverage80%+
Strategic alignmentStakeholder confirmed

Done when: OST complete, top 2-3 prioritized, team aligned.

Phase 3: Solution Testing

MetricTarget
Task completion>80%
Value perception>70% "would use/buy"
Comprehension<10 sec to understand
Key assumptions validated>80% proven

Done when: 5+ users per iteration, core flow usable, value + feasibility confirmed.

Phase 4: Market Viability

MetricTarget
Four big risksAll green/yellow
Channel validated1+ viable
Unit economicsLTV > 3x CAC (estimated)
Stakeholder signoffLegal, finance, ops

Done when: Lean Canvas complete, all risks acceptable, go/no-go documented.

State Tracking Schema

current_phase: "1|2|3|4"
phase_started: "ISO timestamp"
interviews_completed: "count by phase"
assumptions_tracked: "list with risk scores"
opportunities_identified: "list with scores"
decision_gates_evaluated: "G1|G2|G3|G4 status"
artifacts_created: "list of file paths"

Phase Transition Requirements

TransitionGateRequirements
1 to 2G15+ interviews, >60% confirmation, customer words, 3+ examples
2 to 3G2OST complete, top 2-3 identified, scores >8, team alignment
3 to 4G35+ users tested, >80% task completion, core flow usable, validated
4 to handoffG4Lean Canvas complete, 4 risks acceptable, go/no-go, stakeholder sign-off

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

The English summary is being prepared. Showing the original description.

nWave-ai/nWave621Updated Sep 16, 2026

Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation

The English summary is being prepared. Showing the original description.

nWave-ai/nWave621Updated Sep 16, 2026

Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof

The English summary is being prepared. Showing the original description.

nWave-ai/nWave621Updated Sep 16, 2026

Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement

The English summary is being prepared. Showing the original description.

nWave-ai/nWave621Updated Sep 16, 2026

5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance

The English summary is being prepared. Showing the original description.

nWave-ai/nWave621Updated Sep 16, 2026

Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.

The English summary is being prepared. Showing the original description.

nWave-ai/nWave621Updated Sep 16, 2026

See all skills by nWave-ai

Report a problem with this skill