product-vision
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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- product-vision
- description
- 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.
03 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:
- Inspiring - Motivates teams to wake up and commit to the goal
- Achievable - Realistic based on resources, market, and capabilities
- Emotional - Creates meaning and connection
Process
- Review provided company and product information
- Identify the core problem being solved
- Envision the ideal future state for customers and the company
- Draft multiple vision options (3-5 variations)
- Select the strongest vision and briefly explain your rationale
- 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
04 同仓库更多 Skills
tb-writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
tb-using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
tb-test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
tb-subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
tb-scrutinize
Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on /tb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.
tb-requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements