BD product-discovery
Discover external customer problems and product requirements from human stakeholders. Assess customer evidence before investing, or map who to talk to, ask questions that surface hidden assumptions, detect gaps in real time, resolve conflicts, and translate conversations into structured SDD specs. Phase 0 upstream of Spec-Driven Development. Also grill a PRD, interrogate a proposal, poke holes in a spec, or interview its author about an existing draft, one consequential question at a time. Do not use for personal-life discovery (daily-life-discovery), general research without product requirements (research-methodology), or implementation planning.
Discover external customer problems and product requirements from human stakeholders.
As a process D 38/100 · Unfinished process — References files that are not bundled: ../product-methodology/SKILL.md, ../product-design-and-ux/SKILL.md, ../daily-life-discovery/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../product-methodology/SKILL.md - warning
missing-refreference to a missing file: ../product-design-and-ux/SKILL.md - warning
missing-refreference to a missing file: ../daily-life-discovery/SKILL.md - warning
missing-refreference to a missing file: ../research-methodology/SKILL.md - warning
missing-refreference to a missing file: ../implementation-planning/SKILL.md
Process rating: all ten parameters 38/100
- 0Tools and files. 5 referenced file(s) missing: ../product-methodology/SKILL.md, ../product-design-and-ux/SKILL.md, ../daily-life-discovery/SKILL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 2 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Steps. 18 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2434 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 655: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (10 of 10)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.