Craft product mission

Skill alexe-ev/product-plugins/product-strategy/skills/craft-product-mission

Write a clear, actionable product mission statement that defines what the product does, for whom, and why it exists today. Use this skill when a team needs to separate mission (today) from vision (future) and make the mission specific enough to guide decisions.From its SKILL.md

Install

npx -y skills add alexe-ev/product-plugins --skill craft-product-mission

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, 515 tokens by cl100k_base, as published. Nobody here has run it

Craft Product Mission

Purpose

Help teams articulate a mission statement that anchors day-to-day decisions: what the product does, for whom, and what value it delivers right now.

Skill type

Conceptual skill

Use this skill when

The team confuses vision and mission or uses them interchangeably
A mission statement is too vague to guide product trade-offs
A new product area needs a mission before planning begins
Team alignment breaks down because there is no shared "what we do and for whom"

Do not use this skill when

The goal is long-term aspirational direction (use define-product-vision)
The goal is competitive positioning (use define-strategic-positioning)

Required inputs

Target user or customer segment
Core value the product delivers
Product area or type

Optional inputs

Existing mission or vision drafts
Business model context
OKRs or strategic goals

Upstream context

Works best when:

Vision is defined or being developed in parallel
Target segment is identified

If upstream context is missing

Draft a provisional mission and list what must be validated before it can be used to make decisions.

Downstream handoff

Output can feed:

build-portfolio-roadmap-strategy (mission constrains what goes on the roadmap)
set-goals-okrs-kpis (OKRs should map to mission)
develop-positioning-messaging (mission is the backbone of external messaging)

Instructions

Identify who the product serves (specific segment, not everyone).
Identify the core job or problem the product addresses.
Identify the value delivered (outcome, not feature).
Draft a mission statement: "[Product] helps [who] [do what] so they can [outcome]."
Test the draft: is it specific enough to say no to things? Would it exclude irrelevant features?
Flag what is still assumed vs. validated.

Output

Provide:

Mission statement
Who it serves
Core job or problem addressed
Value delivered
Specificity test: what would this mission say no to?
Confidence level: provisional / context-informed / validated
Open questions

Risks / caveats

"Helps everyone do everything better" is not a mission
Mission must be present-tense and achievable — vision is aspirational, mission is operational
If the mission can't be used to reject bad ideas, it's too vague

What ships with it: 3 files

5.0 KB alongside SKILL.md

examples/

Gives 0 of the 12 instructions most product growth skills give in 515 tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-07

Read product marketing context before asking questionsin 24 of 728, across 18 files
Define the ideal customer profilein 21 of 728, across 3 files
Document a rollback plan before deploymentin 21 of 728, across 12 files
Analyze the codebase to understand the productin 19 of 728, across 1 file
Ask clarifying questions about the value propositionin 19 of 728, across 1 file
Search for companies matching the criteriain 19 of 728, across 1 file
Look for signals of immediate needin 19 of 728, across 1 file
Assign a fit score from one to tenin 19 of 728, across 1 file
Identify the target decision-maker rolein 19 of 728, across 1 file
Suggest a personalized contact strategyin 19 of 728, across 1 file
Provide conversation starters for outreachin 19 of 728, across 1 file
Format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

Identify a specific target segment
Identify the outcome delivered
Draft a mission statement using the provided template
Test the draft for specificity
Flag assumptions versus validated facts
Provide the required mission outputs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.