product-vision-strategy
Skill0 starsChanged 7 months agoMITView on GitHub
Set long-term product vision and define the path to success, transforming abstract goals into an actionable strategic framework.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Strategy is Trade-offs: If your strategy doesn't include "what we decisively will NOT do," it is not a strategy.
- Distinctive: line 36
Uniqueness: Ask "Why us? Why now?"
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Vision & Strategy: Vision and Strategic Framework
A product without strategy is just a collection of features.
Checklist
- Define Product Vision — Describe how the world will change because of your product in 3-5 years (The North Star).
- Develop Strategic Pillars — Three key competitive advantages or core capabilities that support the vision.
- Identify Target Customers & Value Proposition (VPC) — Clarify who you are responsible to and what core conflict you are solving.
- Establish Success Criteria — How will strategic progress be quantified?
Core Framework: Strategy Cascade
graph strategy_cascade {
node [shape=box];
Vision [label="Vision\nFuture State"];
Strategy [label="Strategy\nKey Choices"];
Roadmap [label="Roadmap\nExecution Order"];
Metrics [label="Metrics\nSuccess Measurement"];
Vision -- Strategy;
Strategy -- Roadmap;
Strategy -- Metrics;
}Expert Principles
- Strategy is Trade-offs: If your strategy doesn't include "what we decisively will NOT do," it is not a strategy.
- Uniqueness: Ask "Why us? Why now?"
In this repository34 other files it gives its agents.
- agile-scrum-masterySkill
- artifact-provenanceSkill
- brainstormingSkill
- business-acumenSkill
- cross-functional-collaborationSkill
- customer-discoverySkill
- customer-empathySkill
- data-analysisSkill
- gtm-launch-managementSkill
- lean-experimentationSkill
- market-researchSkill
- metrics-definitionSkill
- negotiation-conflict-resolutionSkill
- north-star-metricSkill
- opportunity-mappingSkill
- outcome-ownershipSkill
- presentation-storytellingSkill
- prioritizationSkill
- problem-solvingSkill
- product-definitionSkill
- project-managementSkill
- prototypingSkill
- qa-quality-mindsetSkill
- roadmappingSkill
- spec-driven-designSkill
- stakeholder-managementSkill
- subagent-driven-discoverySkill
- technical-acumenSkill
- user-interviewingSkill
- using-pmpowersSkill
- ux-design-awarenessSkill
- validation-guardSkill
- writing-plansSkill
- written-communicationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

