Generic product context template for creating product vision, goals, and constraints skills. Auto-invoke when user requests product skill creation, product context framework, or strategic alignment templates. Do NOT load during actual product work (use project-specific skills instead).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Generic product context template for creating product vision, goals, and constraints skills. Auto-invoke when user requests product skill creation, product context framework, or strategic alignment templates. Do NOT load during actual product work (use project-specific skills instead).
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.
Generic descriptions ("Information about product...")
No product scope boundaries
Missing trigger terms users will actually mention
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.
Product Context Content Structure
1. Product Vision & Mission
Purpose: Core purpose and long-term aspiration
Product Vision
[ONE_SENTENCE_VISION_STATEMENT]
Example: "Enable every restaurant to offer flexible payment options that increase customer purchasing power while maintaining financial security."
Mission Statement
[ONE_TO_TWO_SENTENCE_MISSION]
Target Outcome: [MEASURABLE_GOAL_OR_IMPACT]
Example: "Increase average transaction value by >30%"
Example: "Reduce merchant setup time from weeks to <24 hours"
Zero business-confidential data (revenue, pricing, specific budgets)
Vision and goals are clear and measurable
Constraints are documented with rationale
Strategic Clarity:
Vision statement is one sentence and inspiring
Success metrics are specific and measurable
Trade-offs are documented with reasoning
Assumptions are testable
Risks have mitigation strategies
User Focus:
Primary personas clearly defined
User goals and pain points specific
UX principles actionable (not generic)
Accessibility requirements clear
Metadata & Tracking:
product-version field indicates current release
Last updated date is current
allowed-tools: [] set (product context is read-only reference)
Category and tags aid discovery
Security & Scope:
File location matches scope (product context in .claude/skills/projects/[product-name]/)
No competitive intelligence or confidential strategy exposed
Reviewed by product owner
Usage Examples
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:
Actual product work (use project-specific skills instead)
Technical implementation details (use ground truth for specs)
Stakeholder information (use stakeholder template)
Frequently changing tactical plans (product context is strategic)
Maintenance & Freshness
Update Triggers:
New product vision or strategic pivot
Major release with significant feature changes
Quarterly goals update
New competitive positioning
Persona evolution based on user research
Review Cadence:
Vision/Mission: Annually or on strategic pivot
Goals/Metrics: Quarterly
Features/Roadmap: Monthly
Constraints/Risks: Ongoing as they change
Version Control:
Update product-version field with product release version
Track changes in git with reference to product release notes
Use semantic versioning for template (1.0.0 → 1.1.0 for additions)
Template Source: Phase 2 requirements + product management best practices
Template Version: 1.0.0
Last Updated: 2025-10-20
Validation: Ready for Phase 2 implementation
