strategic-build

Distinguishes strategic vs tactical work during development using Shreyas Doshi's frameworks and Marty Cagan's empowered teams principles. Use when making architectural decisions, choosing what to build, preventing "product theater", or applying the LNO framework (Leverage, Neutral, Overhead). Helps avoid feature factory and build work that compounds.

Quality

83%

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 skill provides highly actionable frameworks with excellent workflow clarity through decision trees and structured templates. However, it suffers from verbosity—explaining concepts extensively, including multiple real-world examples inline, and repeating key ideas across sections. The content would benefit from aggressive trimming and splitting detailed content into referenced files.

Suggestions

Reduce inline explanations and quotes; Claude understands these PM concepts—focus on the decision criteria and templates only

Move 'Real-World Examples', 'Common Pitfalls', and 'Key Quotes' sections to a separate reference file, keeping only the core frameworks and templates in SKILL.md

Consolidate the three action templates into a single flexible template or move to a templates/ directory with brief inline references

Dimension	Reasoning	Score
Conciseness	The skill contains valuable frameworks but is verbose with extensive explanations, repeated concepts, and quotes that pad the content. The decision tree, templates, and examples could be more condensed while preserving clarity.	2 / 3
Actionability	Provides concrete, copy-paste ready templates (LNO Assessment, Three Levels Check, Pre-Mortem), clear decision trees with specific criteria, and actionable checklists. The frameworks include specific questions to ask and thresholds (e.g., '10+ times', '70% Leverage').	3 / 3
Workflow Clarity	The decision tree provides an explicit sequence with clear branching logic and checkpoints. Each framework has a clear 'How to Apply' section with numbered steps, and the templates guide users through validation at each stage.	3 / 3
Progressive Disclosure	References external files (references/shreyas-doshi-frameworks.md, etc.) appropriately, but the main skill file is monolithic at ~400 lines. The core frameworks, examples, pitfalls, and templates could be split into separate files with the SKILL.md serving as a leaner overview.	2 / 3
	Total	10 / 12 Passed

Description

89%

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 with excellent trigger term coverage and completeness. It clearly identifies its niche through named frameworks and specific product management terminology. The main weakness is that the core actions could be more concrete - describing what the skill actually does beyond 'distinguishes' and 'helps avoid'.

Suggestions

Replace vague verbs like 'distinguishes' and 'helps avoid' with more concrete actions such as 'evaluates decisions against', 'recommends prioritization using', or 'analyzes work items to classify'

Dimension	Reasoning	Score
Specificity	Names the domain (strategic vs tactical work) and references specific frameworks (Shreyas Doshi's, Marty Cagan's, LNO framework), but the actual actions are somewhat vague - 'distinguishes', 'helps avoid' rather than concrete actions like 'analyzes', 'recommends', 'evaluates'.	2 / 3
Completeness	Clearly answers both what (distinguishes strategic vs tactical work using specific frameworks) and when (explicit 'Use when' clause with multiple trigger scenarios: architectural decisions, choosing what to build, preventing product theater, applying LNO framework).	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'architectural decisions', 'choosing what to build', 'product theater', 'LNO framework', 'Leverage, Neutral, Overhead', 'feature factory', 'work that compounds'. These are terms practitioners actually use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with specific named frameworks (Shreyas Doshi, Marty Cagan, LNO) and domain-specific terminology (product theater, feature factory, empowered teams). Unlikely to conflict with generic development or architecture skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

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.