Platform team plans (canonical)
Long-lived Platform planning and specs that were previously under .cursor/plans/ now live here so they are visible in the repo and linkable from the Platform Team Charter.
| File | Topic |
|---|---|
| q2-2026-legal-finance-sales-engineering-roadmap.md | Q2 hub: Legal, Finance, Sales Engineering (links to team vault roadmaps: ../../finance/plans/q2-2026-roadmap.md, ../../sales/plans/q2-2026-sales-engineering-roadmap.md, Legal) |
| platform-initiatives-and-plans-reflection-2026-03.md | Linear initiatives vs. vault plans (reflection) |
| instagantt-to-linear-migration.plan.md | Instagantt → Linear projects/milestones |
| paperclip-platform-railway.plan.md | Paperclip in monorepo + Railway |
| skill-usage-tracking.plan.md | Skill/command/rule usage → Supabase |
| company-okrs-operational-database.plan.md | OKRs / ops data DB migration |
| company-okrs-in-platform.plan.md | Company OKRs in Platform UI (phased) |
| agent-browser-cloud-agents.plan.md | Agent-browser for cloud agents (vs Playwright / MCP); phased spike and standards |
Note: Cursor may still create ephemeral plans under .cursor/plans/ during sessions; copy anything team-facing into knowledge/ (this folder or knowledge/plans/) before treating it as canonical.