Help us improve
Share bugs, ideas, or general feedback.
From skills-toolkit
Generates customizable SKILL.md templates for product context including vision, mission, goals, constraints, and user personas. Invoke when creating product strategy skills for Claude.
npx claudepluginhub youngleadersdottech/young-leaders-tech-marketplace --plugin skills-toolkitHow this skill is triggered — by the user, by Claude, or both
Slash command
/skills-toolkit:product-context-templateThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This template guides the creation of product context skills - strategic information about product vision, goals, constraints, and positioning that helps Claude understand the "why" behind technical decisions. Replace all `[PLACEHOLDER]` values with actual product information.
Guides creation or refinement of PRODUCT.md for product-aware reviews in pre-mortem and vibe workflows.
Creates and maintains a product marketing context document capturing positioning, audience, and messaging. Use at project start to avoid repeating foundational info.
Structures product basics (problem hypothesis, solution, market scope, origin story, business model, competitors, differentiation) via user Q&A and codebase analysis into product-context.md. Use for new projects or direction reviews before persona/LP design.
Share bugs, ideas, or general feedback.
This template guides the creation of product context skills - strategic information about product vision, goals, constraints, and positioning that helps Claude understand the "why" behind technical decisions. Replace all [PLACEHOLDER] values with actual product information.
---
name: [product-name]-context
description: Product context for [PRODUCT_NAME] including vision, goals, and constraints when discussing [FEATURE_AREA_1], [FEATURE_AREA_2], or [USE_CASE]. Auto-invoke when user mentions [PRODUCT_NAME], [KEY_FEATURE], or [TARGET_USER_SEGMENT]. Do NOT load for general [DOMAIN] discussions unrelated to [PRODUCT_NAME].
allowed-tools: []
version: 1.0.0
category: Product
tags: [[product-name], [domain], product-context, strategy]
product-version: [VERSION_OR_RELEASE]
last-updated: [YYYY-MM-DD]
---
Description Engineering Guidance:
✅ DO include:
❌ DON'T use:
Example Good Description:
Product context for EasyPay payment processing including merchant onboarding, flexible leasing, and international support when discussing payment flows, compliance requirements, or merchant experience. Auto-invoke when user mentions EasyPay, merchant setup, or leasing options. Do NOT load for general payment discussions outside EasyPay.
Purpose: Core purpose and long-term aspiration
[ONE_SENTENCE_VISION_STATEMENT]
Example: "Enable every restaurant to offer flexible payment options that increase customer purchasing power while maintaining financial security."
[ONE_TO_TWO_SENTENCE_MISSION]
Target Outcome: [MEASURABLE_GOAL_OR_IMPACT]
[WHERE_PRODUCT_FITS_IN_MARKET][WHAT_MAKES_THIS_UNIQUE][KEY_ADVANTAGE_OVER_ALTERNATIVES]Purpose: Who the product serves and their key characteristics
[PERSONA_NAME]Role: [JOB_TITLE_OR_ROLE]
Key Characteristics:
[PRIMARY_GOAL_1], [PRIMARY_GOAL_2][PAIN_POINT_1], [PAIN_POINT_2][LOW/MEDIUM/HIGH][WHAT_THEY_CAN_DECIDE]Success Metrics (for this persona):
[METRIC_1]: [TARGET_VALUE][METRIC_2]: [TARGET_VALUE][PERSONA_NAME](Repeat structure for secondary/tertiary personas)
Purpose: Measurable objectives and KPIs
[RELEASE_VERSION]| Goal | Success Metric | Target | Current | Status |
|---|---|---|---|---|
[GOAL_1] | [METRIC_NAME] | [TARGET_VALUE] | [CURRENT_VALUE] | [ON_TRACK/AT_RISK/ACHIEVED] |
[GOAL_2] | [METRIC_NAME] | [TARGET_VALUE] | [CURRENT_VALUE] | [ON_TRACK/AT_RISK/ACHIEVED] |
[GOAL_3] | [METRIC_NAME] | [TARGET_VALUE] | [CURRENT_VALUE] | [ON_TRACK/AT_RISK/ACHIEVED] |
[STRATEGIC_GOAL_1]: [DESCRIPTION_AND_WHY][STRATEGIC_GOAL_2]: [DESCRIPTION_AND_WHY][STRATEGIC_GOAL_3]: [DESCRIPTION_AND_WHY]Purpose: Known limitations and strategic trade-off decisions
Performance: [CONSTRAINT_DESCRIPTION]
[WHY_THIS_MATTERS]Scalability: [CONSTRAINT_DESCRIPTION]
[WHY_THIS_MATTERS]Integration: [CONSTRAINT_DESCRIPTION]
[WHY_THIS_MATTERS][CONSTRAINT_DESCRIPTION] (use relative terms, no specific amounts)[CONSTRAINT_DESCRIPTION][CONSTRAINT_DESCRIPTION][REGULATORY_REQUIREMENTS]Trade-off: [WHAT_WAS_DECIDED]
We chose: [OPTION_A]
Over: [OPTION_B]
Because: [RATIONALE]
Date decided: [YYYY-MM-DD]
Revisit if: [CONDITION_THAT_WOULD_CHANGE_DECISION]
Purpose: What the product does (high-level, not implementation details)
[CATEGORY_NAME]Features:
[FEATURE_NAME]
[WHY_THIS_EXISTS][BENEFIT_TO_USER][AVAILABLE/IN_DEVELOPMENT/PLANNED][MUST_HAVE/SHOULD_HAVE/NICE_TO_HAVE][FEATURE_NAME]
(Repeat structure)
| Quarter | Theme | Key Features | Goal |
|---|---|---|---|
[Q1 YYYY] | [THEME] | [FEATURES] | [OBJECTIVE] |
[Q2 YYYY] | [THEME] | [FEATURES] | [OBJECTIVE] |
[Q3 YYYY] | [THEME] | [FEATURES] | [OBJECTIVE] |
Note: Roadmap is directional, subject to change based on customer feedback and market conditions.
Purpose: Design philosophy and UX standards
[PRINCIPLE_1]: [DESCRIPTION]
[HOW_THIS_APPLIES_TO_DECISIONS][PRINCIPLE_2]: [DESCRIPTION]
[HOW_THIS_APPLIES_TO_DECISIONS][PRINCIPLE_3]: [DESCRIPTION]
[HOW_THIS_APPLIES_TO_DECISIONS][WCAG_LEVEL] (e.g., WCAG 2.1 AA)[SPECIFIC_REQUIREMENTS][HOW_ACCESSIBILITY_IS_VALIDATED]Purpose: How product fits in broader ecosystem
| System | Integration Type | Purpose | Status |
|---|---|---|---|
[SYSTEM_1] | [API/WEBHOOK/SDK] | [WHY_INTEGRATED] | [ACTIVE/PLANNED] |
[SYSTEM_2] | [API/WEBHOOK/SDK] | [WHY_INTEGRATED] | [ACTIVE/PLANNED] |
Upstream Dependencies: [SYSTEMS_WE_DEPEND_ON]
Downstream Consumers: [SYSTEMS_THAT_DEPEND_ON_US]
Lateral Partners: [PEER_SYSTEMS_WE_COORDINATE_WITH]
Purpose: Known assumptions and tracked risks
[ASSUMPTION_1]
[WHAT_WOULD_CHANGE][HOW_WE_TEST_THIS][ASSUMPTION_2]
(Repeat structure)
| Risk | Probability | Impact | Mitigation | Owner |
|---|---|---|---|---|
[RISK_1] | [LOW/MEDIUM/HIGH] | [LOW/MEDIUM/HIGH] | [MITIGATION_STRATEGY] | [ROLE_NOT_NAME] |
[RISK_2] | [LOW/MEDIUM/HIGH] | [LOW/MEDIUM/HIGH] | [MITIGATION_STRATEGY] | [ROLE_NOT_NAME] |
Before finalizing product context skill, verify:
Content Quality:
[PLACEHOLDERS] replaced with actual valuesStrategic Clarity:
User Focus:
Metadata & Tracking:
product-version field indicates current releaseallowed-tools: [] set (product context is read-only reference)Security & Scope:
.claude/skills/projects/[product-name]/)Creating New Product Context Skill:
User: "Create a product context skill for EasyPay"
Claude: [Loads this template skill, uses structure to create EasyPay-specific context]
Feature Development Guidance:
User: "Should we add advanced analytics to the merchant dashboard?"
Claude: [Loads product context skill, checks against vision, user personas, and goals]
Response: "Based on product vision of 'simplicity over features' and primary persona being small restaurant owners with low technical proficiency, advanced analytics might violate UX principle #1. Consider progressive disclosure - basic metrics by default, advanced analytics opt-in."
Do NOT Use This Template For:
Update Triggers:
Review Cadence:
Version Control:
product-version field with product release versionTemplate Source: Phase 2 requirements + product management best practices Template Version: 1.0.0 Last Updated: 2025-10-20 Validation: Ready for Phase 2 implementation