product-manager

Manage product registry entries in the PRODUCTS.md vault file.

Updated Apr 14, 2026

Search Tags:#manage #sunset #product-registry #products.md #add-product #update-product

Ready to run

npx skills add https://github.com/viditparashar96/second-brain-claude --skill product-manager-viditparashar96

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-manager
Source: https://github.com/viditparashar96/second-brain-claude/tree/main/skills/product-manager
Command: npx skills add https://github.com/viditparashar96/second-brain-claude --skill product-manager-viditparashar96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain a single source of truth for all organizational products so teams avoid duplicated, outdated, or missing product information and every department can rely on consistent product context.

Core Features & Use Cases

Registry CRUD: Add new products, update existing entries, list products by status, and move products to a Sunset section without deleting history.
Cross-department context: Populate fields that serve sales, engineering, HR, product, and ops (pricing, tech stack, owner, competitive edge) so downstream skills can consume accurate product data.
Governance & Logging: Check for duplicates, update cross-reference tables and relationships, and append a one-line activity log to daily memory via the MCP log_note tool.

Quick Start

Add a new product named Acme Chat with category AI/Voice, status planned, owner Product Team, a concise description, and the top three key features.

Frequently Asked Questions about product-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain a centralized product registry to avoid duplicated product information?▼

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.

What is the best way to sunset a product without deleting its catalog history?▼

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.

How do I add a new product to the catalog with cross-department context like pricing and tech stack?▼

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.

Does the product registry check for duplicate entries when onboarding new products?▼

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.

Can I use this registry management approach for roadmap planning across different teams?▼

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.

Why does updating a product entry require logging actions via daily memory?▼

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.