# product-context

> Provides domain knowledge about 365 Retail Markets product ecosystem, client relationships, integration landscape, and team structure. Auto-invoked to resolve shorthand, enrich card generation, and provide organizational context. References/ directory contains updatable product domain knowledge.

- Author: jeremybrice
- Repository: jeremybrice/product-forge-marketplace
- Version: 20260209060811
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-09
- Source: https://github.com/jeremybrice/product-forge-marketplace
- Web: https://mule.run/skillshub/@@jeremybrice/product-forge-marketplace~product-context:20260209060811

---

---
name: product-context
description: "Provides domain knowledge about 365 Retail Markets product ecosystem, client relationships, integration landscape, and team structure. Auto-invoked to resolve shorthand, enrich card generation, and provide organizational context. References/ directory contains updatable product domain knowledge."
---

# Product Context Skill

## Purpose

This skill enables Claude to understand and navigate 365 Retail Markets' product ecosystem without requiring explicit explanation during workflows.

**Key capabilities:**

- **Resolve shorthand references** — When a user says "the CV Cooler thing" or "PepsiCo initiative," Claude resolves to the actual product/module/client from the domain taxonomy without asking for clarification
- **Enrich card generation** — When creating Initiatives, Stories, or Epics, Claude automatically tags products, modules, and clients based on conversation context
- **Provide organizational context** — Claude understands team structure, stakeholder roles, and client relationships to surface relevant information
- **Maintain updatable knowledge** — The references/ directory is the single source of truth for product domain knowledge and can be updated at runtime

## How to Use This Skill

On every invocation, Claude should:

1. **Check for domain knowledge** — Before responding, scan the references/ files if context involves products, modules, integrations, clients, or team coordination
2. **Resolve references** — Use `taxonomy.md` to map user shorthand (e.g., "CV Cooler") to canonical product/module names
3. **Understand dependencies** — Use `integrations.md` to grasp how products depend on each other and external systems
4. **Identify stakeholders** — Use `clients.md` and `teams.md` to determine who cares about the work and who needs to be involved
5. **Tag appropriately** — When generating cards, apply the correct product, module, and client tags from the taxonomy

## Updating Domain Knowledge

The references/ files are updatable at runtime. Three scenarios trigger updates:

**1. Explicit user request**
"Add UMS Portal to the taxonomy" or "Update the PepsiCo client profile"

**2. During card workflows**
When Claude encounters a product, module, or integration not in the reference files, flag it to the user and offer to add it in the next workflow step.

**3. Dedicated maintenance**
A user explicitly requests context updates via "/forge update-context" or similar trigger for periodic knowledge review.

**Updating process:**
- Edit the specific reference file directly (don't rewrite entire files)
- Add or modify the relevant entry
- Confirm the update to the user

## Memory Contribution (Optional)

When Product Forge discovers interaction-derived context during workflows, contribute to the shared Productivity memory system:

- **People insights** → `memory/people/{name}.md`
  - Example: "Anton prefers architecture diagrams in technical stories"
- **Project context** → `memory/projects/{name}.md`
  - Example: "PepsiCo CV Cooler rollout shifted from Q3 to Q4"
- **PM-specific terms** → `memory/glossary.md`
  - Example: "ROM = Return on Margin, DEX = Data Exchange, MDB = Multi-Drop Bus"

**Note:** Only contribute if `memory/` directory exists (Productivity plugin is loaded). If not, degrade gracefully—the references/ files still provide core domain knowledge.

## Reference Files

- **`taxonomy.md`** — Product lines, modules, and their descriptions
- **`integrations.md`** — Integration landscape, protocols, and external systems
- **`clients.md`** — Client relationships, key initiatives, and requirements patterns
- **`teams.md`** — Team structure, leadership, and organizational notes