Add, update, and manage products in the organization's product registry (PRODUCTS.md)
Manage the organization's product registry (PRODUCTS.md). This is the single source of truth for all products — every department skill pulls from this file for context. Keep it accurate and up to date.
add — Add a New ProductGather product details — Ask for (or extract from user input):
Check for duplicates — Read ~/.second-brain/vault/PRODUCTS.md and verify no product with the same name exists
Add to PRODUCTS.md — Append the new product entry under the appropriate section (Active Products, In Development, etc.) following the template format:
### {Product Name}
- **Category:** {category}
- **Status:** {status}
- **Owner:** {owner}
- **Target Audience:** {audience}
- **Description:** {description}
- **Key Features:** {features}
- **Tech Stack:** {tech stack}
- **Pricing Model:** {pricing}
- **Competitive Edge:** {competitive edge}
- **Key Clients:** {clients}
- **Known Issues:** {issues}
- **Roadmap:** {roadmap}
Update Cross-Department Quick Reference table at the bottom of PRODUCTS.md
Update Product Relationships section if this product relates to existing ones
Log to daily — Append: - **HH:MM** — [PRODUCT] Added to registry: {product name} ({status})
update — Update an Existing Product~/.second-brain/vault/PRODUCTS.md- **HH:MM** — [PRODUCT] Updated: {product name} — changed: {what changed}list — List All Products~/.second-brain/vault/PRODUCTS.mdremove — Sunset a Product- **HH:MM** — [PRODUCT] Sunset: {product name} — reason: {reason}Every department skill automatically has access to PRODUCTS.md because it's injected at session start. Here's how:
Sales skills (deal-prep, proposal-drafter, follow-up) → Pull product features, pricing, competitive edge, key clients for the relevant product
HR skills (onboarding-checklist, performance-review) → Pull which products a team member's department owns
Product skills (prd-drafter, okr-tracker, stakeholder-update) → Pull current product status, roadmap, known issues
Ops skills (sop-creator, compliance-checklist) → Pull tech stack, deployment context, SLAs
Engineering skills (code-review, incident-response) → Pull tech stack, known issues, architecture context
Cloud memory: After completing this workflow, call the log_note MCP tool with a one-line summary of what was done. Example: log_note("Completed eng-plan for School Cab — 9 phases, 22 days")