discover

Clarify ambiguous product problems into a concrete discovery brief.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/LaPaGaYo/nexus --skill discover-lapagayo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discover
Source: https://github.com/LaPaGaYo/nexus/tree/main/skills/canonical/discover
Command: npx skills add https://github.com/LaPaGaYo/nexus --skill discover-lapagayo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nexus discovery clarifies ambiguous product problems and frames them into a concrete discovery brief that guides later framing and governance.

Core Features & Use Cases

  • Canonical problem framing: guides users from vague input to a defined discovery scope.
  • Evidence-driven framing: surfaces necessary information to support decision making in project planning.
  • Governance-ready outputs: produces artifacts that feed into Nexus lifecycle stages and reviews.

Quick Start

Tell Nexus to begin a discovery run for your current project to clarify the problem space.

Frequently Asked Questions about discover

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

FAQPage Schema
How do I clarify ambiguous product problems for early-stage discovery?

Problem framing works by guiding you from a vague input to a defined discovery scope. It surfaces necessary evidence to support decision making, producing governance-ready artifacts that feed into later lifecycle stages.

When do I need to define discovery scope for a product lifecycle?

You need to define discovery scope when you are unsure what to build and require early-stage problem space exploration. It produces a concrete discovery brief that feeds directly into Nexus lifecycle stages and reviews.

How do I start a discovery run to frame a product problem?

To start a discovery run, you instruct your environment to begin discovery for your current project. This initiates canonical problem framing, guiding you from ambiguous input to a concrete discovery scope.

Do I need existing Nexus artifacts to generate governance-ready outputs?

Yes, clarifying ambiguous problems requires access to existing Nexus artifacts and governance rules. These ensure the generated discovery brief aligns with repo-visible outputs and lifecycle requirements.

What is the best way to frame a discovery brief for project planning?

The best way to frame a discovery brief is through evidence-driven framing. This approach surfaces necessary information to support decision making, transforming vague input into a concrete scope for project planning.

What are the limitations of using problem framing for scope definition?

A limitation of problem framing is that it applies strictly to early-stage problem space exploration and scope definition. It requires existing Nexus artifacts and does not handle later lifecycle execution stages directly.