agentleFS
yuusakuriyuusakuri/agent-skills/skills/product-vision/SKILL.md

product-vision

Skill2 starsChanged 22 days agoMITView on GitHub

Brainstorm an inspiring, achievable, and emotional product vision that motivates teams and aligns stakeholders. Use when defining or refining a product vision, creating a vision statement, or aligning the team around a shared direction.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

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
  1. Distinctive:

    Consider the perspective of customers, employees, and investors

    line 43
  2. Distinctive:

    Avoid jargon; use clear, emotionally resonant language

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Product Vision

Metadata

  • Name: product-vision
  • Description: Brainstorm an inspiring, achievable, and emotional product vision. Use when defining or refining product vision, aligning teams around a north star, or creating a vision statement.
  • Triggers: product vision, vision statement, create vision, inspiring vision, north star vision

Domain Context

A product vision answers: "How can we inspire people? What are we aspiring to achieve? What values do we uphold?" Vision evolves with strategy — it's a living statement, not a one-time exercise. It should make people feel something, not just understand the direction.

Instructions

You are a veteran product leader developing a compelling product vision.

Your task is to brainstorm a product vision for $ARGUMENTS.

Input Requirements

  • Information about your company and product (you may read files from the user's workspace)
  • Current state, market positioning, or any relevant context

Output

Provide a vision statement that is:

  1. Inspiring - Motivates teams to wake up and commit to the goal
  2. Achievable - Realistic based on resources, market, and capabilities
  3. Emotional - Creates meaning and connection

Process

  1. Review provided company and product information
  2. Identify the core problem being solved
  3. Envision the ideal future state for customers and the company
  4. Draft multiple vision options (3-5 variations)
  5. Select the strongest vision and briefly explain your rationale
  6. Highlight how this vision aligns with company values and market opportunity

Notes

  • A great vision is memorable and can be communicated in one sentence
  • Balance ambition with credibility
  • Consider the perspective of customers, employees, and investors
  • Avoid jargon; use clear, emotionally resonant language

Further Reading

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.