Skip to main content
skill CX Codex

north-star-vision — Claude Code skill: what it does, how to install

Articulates a long-horizon product vision across 1-year, 2-3 year, and 5+ year horizons. Useful when a team lacks a clear strategic direction.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill north-star-vision -a claude-code
Open on GitHub

What north-star-vision does

The skill establishes a framework for product strategy. It defines a north-star vision with a single-sentence vision statement, 3 to 5 design pillars, narrative scenarios, and milestone success criteria.

Planning is split across three horizons. These cover tangible improvements in 1 year, experience shifts over 2 to 3 years, and transformations beyond 5 years. The process involves research synthesis, workshops, narrative drafting, and validation.

For scoping near-term tasks, this skill is unsuitable because the author points to design-brief. Use this only when you need to resolve strategic ambiguity.

What it helps with

  • define a long-horizon product vision statement
  • establish 3 to 5 design pillars for product differentiation
  • map product scenarios across 1-year, 2-3 year, and 5+ year horizons
  • specify qualitative signals and quantitative success metrics

Example prompts for the agent

  • Help define a north-star vision for our product with 3-5 design pillars.
  • Draft concrete vision scenarios for 1-year, 2-3 year, and 5+ year horizons.

How to install north-star-vision

1Skills CLI (Vercel)

npx skills add Owl-Listener/designer-skills --skill north-star-vision -a claude-code

2Manually: put the files in place

~/.claude/skills/north-star-vision/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/north-star-vision/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about north-star-vision

How do I install north-star-vision in Claude Code?

Run npx skills add Owl-Listener/designer-skills --skill north-star-vision -a claude-code. You can also place the file directly into ~/.claude/skills/north-star-vision/SKILL.md.

What does north-star-vision do?

It provides a structured workflow to articulate product vision statements, design pillars, narrative scenarios, and success metrics across multiple time horizons.

When should you use design-brief instead of north-star-vision?

Switch to design-brief if you need to scope an immediate, near-term project. The north-star skill focuses on long-term strategy from 1 to 5+ years.

Source text

SKILL.md · MIT
---
name: north-star-vision
description: Articulate a long-horizon product vision that aligns teams and anchors strategy. Use when direction is contested or absent. For near-term project scope, use `design-brief`.
---
# North Star Vision
You are an expert in articulating inspiring product visions that unite teams and guide direction.
## What You Do
You help teams define a north-star vision — a compelling future state that inspires alignment and guides trade-offs.
## Vision Components
- **Vision Statement** — Who, what experience, why it matters (one sentence)
- **Design Pillars** — 3-5 strategic focus areas defining differentiators
- **Vision Scenarios** — Concrete narrative stories of the future experience
- **Success Criteria** — Qualitative signals, quantitative metrics, milestones
## Time Horizons
- Near-term (1yr): tangible improvements
- Mid-term (2-3yr): major experience shifts
- Long-term (5+yr): aspirational transformation
## Process
Research synthesis, aspiration workshop, narrative writing, validation, communication.
## Best Practices
- Inspiring but grounded in real needs
- Broad enough for unknowns
- Used actively in reviews and planning
- Connected to daily work through pillars

© Owl-Listener · MIT · Owl-Listener/designer-skills

Similar skills

Everything for Design →

From the same set109

design-system-adoption Builds an adoption strategy and enablement materials when teams are bypassing an existing design system. It helps plan education, migration support and measurement. CX Codex +1 2,000installs team-workflow Designs an operating cadence for design teams, covering task tracking, regular rituals, and developer handoff. Helpful when day-to-day design collaboration lacks structure. CX Codex +1 2,000installs opportunity-framework Turns a pile of possible improvements into a ranked roadmap using impact-effort and RICE. Handy when ideas outnumber capacity. CX Codex +1 2,000installs design-review-process A skill that sets four review gates for design work, from concept to implementation QA. Useful when things ship without a consistent review step. CX Codex +1 2,000installs test-scenario Writes usability test scenarios with realistic context, success criteria and facilitation notes. Useful once the study is planned and the tasks are still missing. CX Codex +1 2,000installs stakeholder-alignment Builds alignment artifacts: a stakeholder map, RACI matrix, decision rights and a communication plan. Useful when unclear ownership stalls decisions. CX Codex +1 2,000installs metrics-definition Defines UX metrics and KPIs that connect design decisions to measurable outcomes. Useful when deciding what to measure before tracking changes. CX Codex +1 2,100installs diary-study-plan Walks you through designing a diary study: prompts, cadence, duration, participant criteria and an analysis frame. CX Codex +1 2,100installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor