continuous-discovery

Implements Teresa Torres' continuous discovery habits for weekly customer contact, opportunity solution trees, and assumption testing. Use when building discovery processes, conducting user research, validating assumptions, or establishing product trio workflows.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive and highly actionable skill for continuous discovery practices with excellent templates and decision trees. However, it suffers from verbosity (explaining concepts Claude knows, lengthy examples) and could benefit from splitting content across multiple files. The workflow clarity and actionability are strong, making it immediately usable despite length concerns.

Suggestions

Remove explanatory content Claude already knows (e.g., why product trios work together, what each role does) to reduce token usage by ~20%

Move 'Real-World Examples', 'Key Quotes', and 'Common Pitfalls' to a separate EXAMPLES.md or REFERENCE.md file, keeping SKILL.md as a lean overview with links

Consolidate the templates into a separate TEMPLATES.md file and reference it from the main skill

Dimension	Reasoning	Score
Conciseness	The skill contains useful frameworks but is verbose in places, explaining concepts like what a product trio is and why they work together that Claude likely already knows. Some sections like 'Key Quotes' and 'Real-World Examples' add bulk without proportional value.	2 / 3
Actionability	Provides highly actionable templates (Weekly Discovery Plan, Interview Snapshot, Opportunity Solution Tree, Assumption Test Plan) that are copy-paste ready. Decision trees give concrete guidance for common scenarios, and the Quick Start Guide provides specific week-by-week steps.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with explicit checkpoints. The decision trees provide clear branching logic, the Quick Start Guide has week-by-week progression, and templates include checkbox validation steps throughout the discovery process.	3 / 3
Progressive Disclosure	The skill references related skills at the end but is largely monolithic at ~400 lines. The frameworks, templates, examples, and quick reference could be split into separate files. The 'Related Skills' section shows good cross-referencing but the main content lacks progressive structure.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly identifies a specific methodology (Teresa Torres' continuous discovery habits), lists concrete capabilities, and provides explicit trigger guidance. The description uses third person voice correctly and includes domain-specific terminology that would help Claude accurately select this skill when users discuss product discovery practices.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'weekly customer contact, opportunity solution trees, and assumption testing' along with 'building discovery processes, conducting user research, validating assumptions, establishing product trio workflows'.	3 / 3
Completeness	Clearly answers both what ('Implements Teresa Torres' continuous discovery habits for weekly customer contact, opportunity solution trees, and assumption testing') AND when ('Use when building discovery processes, conducting user research, validating assumptions, or establishing product trio workflows').	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'discovery', 'user research', 'validating assumptions', 'product trio', 'opportunity solution trees', 'customer contact'. These are terms practitioners in product discovery would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive by naming a specific methodology (Teresa Torres' continuous discovery habits) and unique concepts like 'opportunity solution trees' and 'product trio workflows' that are unlikely to conflict with generic product or research skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (544 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: menkesu/awesome-pm-skills
Commit: 53530ef

Reviewed: 3 months ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.