Validate problem space and stakeholder readiness before PRD initiation.
npx skills add https://github.com/ilandahan/AID --skill aid-discovery
Please help me install this Agent Skill. Skill: aid-discovery Source: https://github.com/ilandahan/AID/tree/main/.claude/skills/aid-discovery Command: npx skills add https://github.com/ilandahan/AID --skill aid-discovery
This Skill guides early discovery by validating the problem space, identifying stakeholders, and defining success metrics to support a confident go/no-go decision on PRD.
Invoke aid-discovery to validate the problem space, identify stakeholders, define success metrics, and decide whether to proceed to the PRD.
High-intent search queries and answers about installing and using this skill.
Validating a problem statement before a PRD requires a structured discovery process to map stakeholders and define success metrics. This framework applies an SCQ problem statement template and a phase-gate go/no-go checklist to confirm problem clarity and stakeholder alignment across product, tech, and QA teams.
A phase-gate go/no-go decision framework is a checkpoint process used during project initiation to validate problem space readiness. It evaluates stakeholder alignment and defined success metrics to determine whether cross-functional teams should proceed with drafting a full PRD.
You can map stakeholders and define success metrics at kickoff by applying a structured discovery template. This process identifies key stakeholders across product, tech, and QA teams and articulates success criteria to ensure alignment before advancing to PRD.
Yes, securing stakeholder alignment across product, tech, and QA teams is required before drafting a PRD. A discovery checklist validates problem space readiness and confirms that cross-functional teams agree on the SCQ problem statement and success metrics.
The best way to structure early product discovery for cross-functional teams is using a reference-ready framework with templates for problem statements and stakeholder maps. This enforces a structured discovery checklist that aligns product, tech, and QA teams before PRD.
You should use a discovery checklist instead of immediately writing a PRD when project initiation lacks a clear SCQ problem statement, defined success metrics, or stakeholder consensus. It enforces a phase-gate go/no-go decision to validate problem space readiness and prevent misaligned development.
soeirooCreate structured design briefs with problem statements, audience, constraints, and success criteria.
phoenicisfGuide product discovery and create comprehensive product briefs.
fengqiliuFacilitate cross-team stakeholder alignment and conflict resolution for product managers.
MrAlexisCordGuide MVP definition, scoping, and validation using lean startup methods.
