product-manager

To maintain a centralized product registry, add, update, list, or sunset products in a single source of truth file. This prevents duplicated, outdated, or missing entries so every department can rely on consistent product context.

Sunsetting a product involves moving its entry to a dedicated Sunset section within the product registry. This preserves the historical record without deletion, while still updating cross-references and logging the action.

Adding a new product requires writing a centralized entry that populates fields serving sales, engineering, and HR. You add the product name, category, status, owner, description, and top key features to the registry file.

Yes, the product registry checks for duplicates when adding new entries. It reads the current catalog file, verifies the product does not already exist, updates section placement and cross-links, and logs the action.

Yes, you can use the product registry for roadmap planning and cross-department reference. It maintains accurate product data including owner, status, and competitive edge so downstream skills can consume the context.

Updating a product entry requires logging actions to ensure governance and traceability. It appends a one-line activity log to daily memory, maintaining an accurate history of registry modifications for organizational audits.