dev-vision

Generate project vision statements and record goals in specs/01-vision.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-vision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-vision
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/dev-methodology/skills/dev-vision
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-vision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides product teams to define a clear project vision and strategic direction, aligning stakeholders and setting a concrete path for the release.

Core Features & Use Cases

  • Guided discovery: Elicits user needs, constraints, and success criteria through a structured interview flow.
  • Vision framing: Generates multiple concise vision statements and maps them to strategic objectives.
  • Documentation in specs: Outputs to specs/01-vision.md with goals, personas, metrics, constraints, and assumptions.

Quick Start

Answer the guided prompts to generate the Vision and save it to specs/01-vision.md

Frequently Asked Questions about dev-vision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a structured product vision and why do I need it for roadmap planning?

A structured product vision defines your project's strategic direction, user needs, and success metrics. You need it during early product discovery to align stakeholders and set a concrete path for your release roadmap.

How do I define project strategy and align stakeholders effectively?

You define project strategy by running a guided discovery interview that elicits user needs, constraints, and success criteria. This process generates multiple concise vision statements mapped to strategic objectives to align stakeholders.

Can I generate multiple product vision options before committing to a roadmap?

Yes, you can generate multiple product vision options. The skill outputs several concise vision statements during early discovery, allowing you to compare strategic directions before finalizing your roadmap and saving to specs.

What format should project goals and personas be saved in for product strategy?

Project goals and personas should be saved in a markdown file named specs/01-vision.md. This format captures goals, personas, metrics, constraints, and assumptions to document the product vision.

How do I capture user needs and success metrics during product discovery?

You capture user needs and success metrics by answering structured workflow prompts. This guided interview flow elicits constraints and criteria, records them, and outputs the data into your project specifications.

Is a guided interview flow necessary for defining a project vision?

A guided interview flow is necessary for defining a project vision because it systematically elicits goals, user needs, constraints, and success criteria, ensuring comprehensive strategic alignment rather than relying on ad-hoc planning.