Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Define Vision

ASecurity

Define the product vision, target customer, and positioning for a validated opportunity. Start of the PDLC Strategy phase; writes the product-level vision anchor.

10 stars
0 votes
0 copies
0 views
Added 10/6/2026
documentationgorails

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add tomzx/agents --skill define-vision --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Define Vision?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Define Vision
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tomzx-define-vision/badge)](https://www.skillsdirectory.com/skills/tomzx-define-vision)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: define-vision
description: Define the product vision, target customer, and positioning for a validated opportunity. Start of the PDLC Strategy phase; writes the product-level vision anchor.
argument-hint: "[initiative-id]"
---

# Define Vision

Turns a validated opportunity into a product vision and positioning statement. This skill writes the product-level anchor consumed by every downstream phase: who it is for, what change it creates, and why it wins.

## Prerequisites

- Apply the shared PDLC conventions in `skills/pdlc/references/shared.md`.
- A validated opportunity (Validate gate `proceed`): `opportunity-tree.md` and `experiment-result.md`.

## Steps

1. State the target customer precisely (the ICP, not "everyone"). Reference segments from `market.md`.
2. Articulate the vision: the future where the customer's problem is solved. One sentence a stranger could repeat.
3. Write the positioning statement: *For [target], who [struggle], our product is [category] that [key benefit]. Unlike [alternative], we [differentiation].* Tie differentiation to gaps from `competitors.md`.
4. Define what winning looks like in 12 months — the target state, not a feature list.
5. State explicit non-goals: who and what is out of scope, to prevent vision creep.
6. Write the result to `.pdlc/context/vision.md` (the product-level anchor) **and** leave a pointer in the initiative directory noting which initiative established it.

## Output Format

Use the template at `skills/pdlc/templates/context/vision.md`. Because vision is product-level, it lives under `.pdlc/context/`, not the initiative directory. If multiple initiatives coexist, merge rather than overwrite, and note conflicts.

## Outcome

If `$OUTCOME_YAML` is set, emit `verdict: drafted`.

## Completion Checklist

- [ ] Target customer is specific (an ICP, not "all users")
- [ ] Vision is one repeatable sentence
- [ ] Positioning names a concrete alternative and a concrete differentiation
- [ ] Non-goals stated

## Next Step

Load `set-goals` to translate the vision into measurable objectives and guardrails.

Attribution

tomzxtomzx
View sourceSee grades on GitHubMore from tomzx →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

Architecture Diagram Creator

Create comprehensive HTML architecture diagrams with data flows, business context, and system architecture.

6661 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in W...

1798860 votes
View all in documentation →