agentic-engineering-discovery

Validate product problems and produce an approved discovery brief before specification.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-discovery-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentic-engineering-discovery
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/skills/agentic-engineering-discovery
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill agentic-engineering-discovery-dagimalemayehuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into building solutions before confirming the problem is real, leading to wasted effort on unclear scope, conflicting stakeholder needs, and weak product evidence. This Skill structures the discovery phase so users, outcomes, constraints, and success metrics are explicit before any specification begins. ## Core Features & Use Cases - Problem Validation: Separates observed problems from assumptions and proposed solutions using structured interview and research techniques. - Discovery Brief Generation: Produces an approved brief covering target users, jobs and pain points, desired outcomes, alternatives, constraints, non-goals, assumptions, risks, and measurable success criteria. - Bounded Scope Control: Stops at problem acceptance rather than inventing a solution, keeping discovery distinct from product specification. - Use Case: You have an empty-folder product idea with conflicting stakeholder input. Use this Skill to interview stakeholders, gather evidence, and deliver an approved discovery brief that the team can confidently hand off to specification. ## Quick Start Use $agentic-engineering-discovery to clarify the product problem and desired outcomes for my new project idea.

Frequently Asked Questions about agentic-engineering-discovery

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

FAQPage Schema
How do I validate a product idea before building it?▼

Run a structured discovery phase that separates observed problems from assumptions and proposed solutions. Document target users, jobs, pain points, desired outcomes, and measurable success criteria in an approved discovery brief before writing any specification.

What should a product discovery brief include?▼

A discovery brief should cover target users, jobs and pain points, desired outcomes, alternatives, constraints, non-goals, assumptions, risks, and measurable success criteria. It stops at problem acceptance and does not include solution specifications.

When should I use a discovery phase instead of going straight to specification?▼

Use discovery when scope is unclear, stakeholder needs conflict, product evidence is weak, or users, outcomes, non-goals, and success metrics are not yet explicit. It prevents building solutions for unvalidated problems.

Can discovery be combined with research or stakeholder interviews?▼

Yes, the workflow supports discovery interviews as the core method, with optional techniques like document-grounded questioning, zooming out for context, or bounded research added only when needed to strengthen evidence.

What are the limitations of a discovery-only workflow?▼

Discovery deliberately stops at problem acceptance and does not produce product specifications, designs, or implementation plans. Teams needing immediate technical output must hand the approved brief to a separate specification phase.