knowledge-opslisted

# Knowledge Ops ## Goal Keep product and operations knowledge findable, owned, current, structured, and safe enough for PM Copilot to use as context, structured reference, document prototype, or engineering handoff. ## Workflow 1. Inventory the knowledge source: Notion, Confluence, Google Drive, Obsidian, Markdown, repo docs, support macros, or exported files. 2. Identify canonical owners, last-reviewed dates, audience, lifecycle state, and source-of-truth boundaries. 3. Check each document for 5W2H completeness: who, what, when, where, why, how, and cost/effort. 4. For runbooks and SOPs, verify trigger, owner, prerequisites, step owner, expected duration, success signal, failure signal, rollback, escalation, and audit trail. 5. Detect knowledge-base hygiene issues: stale docs, orphan pages, duplicate docs, conflicting definitions, missing owners, missing links, unreviewed policy content, and outdated screenshots. 6. Prioritize cleanup by usage, risk, staleness, compliance impact, and dependency count. 7. Produce rewrite/archive/merge/keep recommendations with owners and due dates. 8. For structured references, define the field dictionary, stable IDs, source status, review status, owner, access date, unknown-value handling, and engineering handoff notes. 9. For hierarchical or rules-heavy references, structure entities, fields, rules, decisions, children, conditions, defaults, enums, limits, source facts, and product decisions before rendering Markdown or HTML. 10. For mo