recipe-vision
Skill7 starsChanged 3 months agoMITView on GitHub
Defines or updates product vision, outcomes, NSM, and decision-relevant design principles. Use when starting a product, changing strategy, or reassessing outcomes.
In this repository15 other files it gives its agents.
- blueprint-standardsSkill
- business-contextSkill
- design-perspectiveSkill
- hypothesis-disciplineSkill
- prd-standardsSkill
- product-principlesSkill
- prototype-guideSkill
- recipe-blueprintSkill
- recipe-defineSkill
- recipe-discoverSkill
- recipe-personaSkill
- recipe-prototype-promptSkill
- recipe-refine-visualsSkill
- recipe-reflectSkill
- recipe-validateSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Context: Create or update docs/product/vision.md with Product Outcomes, Business Outcomes, NSM, design principles, and strategic priorities.
- Very specific: line 25
Use references/vision-template.md to structure the vision:
- Distinctive: line 38
Update specific sections based on trigger
- Distinctive: line 49
When the current request includes cycle planning, define priorities:
- Distinctive: line 52
Document strategic bets (outcome-level hypotheses)
- Very specific: line 66
Write or update docs/product/vision.md
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Context: Create or update docs/product/vision.md with Product Outcomes, Business Outcomes, NSM, design principles, and strategic priorities.
Execution Decision Flow
1. Context Assessment
Input: Use the path or text supplied with the explicit skill invocation. If no input was supplied and the target cannot be inferred unambiguously, ask for it.
| Situation | Mode | Action |
No docs/product/vision.md exists | Create | Full vision definition |
| Vision exists, triggered by reflection | Update | Review and update specific sections |
| Vision exists, strategic pivot | Update | Re-evaluate outcomes and priorities |
2. Vision Definition
Use references/vision-template.md to structure the vision:
New Product (Create Mode)
- Product Vision: What does this product aspire to become? (2-3 sentences)
- Design Vision: How should the product feel to users?
- Business Outcomes: What business results does the product contribute to?
- Product Outcomes: What team-controllable product goals drive those business results?
- NSM: What single metric connects Product Outcomes to Business Outcomes?
Existing Product (Update Mode)
- Review current vision against
docs/product/learnings.mdwhen that file exists - Assess whether Product Outcomes are still the right targets
- Evaluate NSM — still the right connecting metric?
- Update specific sections based on trigger
3. Design Principles
Define or review the small set of product-specific design principles needed to resolve recurring design trade-offs:
- Each principle should resolve a specific design trade-off
- Principles guide all design decisions across the product
- Write to
docs/product/design-principles.md
4. Strategic Priorities
When the current request includes cycle planning, define priorities:
- Map priorities to Product Outcomes
- Identify key Opportunities per priority
- Document strategic bets (outcome-level hypotheses)
Present the complete vision to the user for the product-strategy decision:
- Product vision and design vision
- Outcome structure (Business → Product → NSM)
- Design principles
- Strategic priorities for current cycle
- Strategic bets with confidence levels
End the current turn with the vision draft as the workflow output. Write files only after the user confirms that draft in a later turn.
5. File Output
After that confirmation:
- Write or update
docs/product/vision.md - Write or update
docs/product/design-principles.md
Scope Boundaries
Included: Vision definition, outcome structure, NSM, design principles, strategic priorities Not included: Opportunity discovery (→ recipe-discover), persona definition (→ recipe-persona), reflection/distillation (→ recipe-reflect)
Completion
The workflow is complete when the confirmed vision and applicable design principles are written, or a no-change result is reported with any unresolved strategy decision.
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.

