Principal PM Dennis Yang uses the AI-powered IDE Cursor not for coding, but as a central workspace for writing PRDs in Markdown, managing them with Git, and connecting to tools like Jira and Confluence. This consolidates the PM workflow into a developer-centric environment.

To create a cohesive product across multiple teams, GitHub uses a framework that forces alignment upfront. By ensuring all teams first deeply understand the problem and collectively identify solutions, the final execution is naturally integrated, preventing a disjointed experience that mirrors the org structure.

A project-level second brain acts as a central, collective intelligence for the entire team. When designers add Figma files and principles, and meeting notes are auto-ingested, PMs can have higher-level conversations with stakeholders, moving beyond basic information exchange to strategic discussion.

To maximize AI's impact, treat LLM skills and prompts like a centralized codebase. When one person discovers a better technique, it should be integrated into a shared, version-controlled repository, ensuring the entire team benefits from individual learnings.

Manage collective team context—docs, queries, research—in a version-controlled repository. Everyone, including non-technical members like ops and strategy, contributes via pull requests, creating a single, evolving source of truth for AI agents and humans.

Instead of using siloed note-taking apps, structure all your knowledge—code, writing, proposals, notes—into a single GitHub monorepo. This creates a unified, context-rich environment that any AI coding assistant can access. This approach avoids vendor lock-in and provides the AI with a comprehensive "second brain" to work from.

Moving PRDs and other product artifacts from Confluence or Notion directly into the codebase's repository gives AI coding assistants persistent, local context. This adjacency means the AI doesn't need external tool access (like an MCP) to understand the 'why' behind the code, leading to better suggestions and iterations.

The current model of separate design files and codebases is inefficient. Future tools will enable designers to directly manipulate production code through a visual canvas, eliminating the handoff process and creating a single, shared source of truth for the entire team.

The best products are built when engineering, product, and design have overlapping responsibilities. This intentional blurring of roles and 'stepping on each other's toes in a good way' fosters holistic product thinking and avoids the fragmented execution common in siloed organizations.